Re: [OT] Design Question : People getting married
Re: [OT] Design Question : People getting married
- Subject: Re: [OT] Design Question : People getting married
- From: John Kestner <email@hidden>
- Date: Wed, 23 Feb 2005 23:30:58 -0700
Alternately, you could freeze the person's name at the time of
publication by having a name field in the Publication table that may be
duplicated from its associated Member name. You'll still know the
author's current name because there's a relationship between the two.
You would do a similar thing in online stores - a product's price may
change, but the price that a customer ordered the product at had better
not.
John
On Feb 23, 2005, at 8:56 PM, Ken Anderson wrote:
Why not have an entity that sits inbetween the Person and the
Publication? Maybe call it Alias or Representation. So you could
have:
Person <-->> Alias <-- Publication
This way, you could handle name differences including ghost writers,
etc. The Publication would always point to the same alias, and that
alias, to a person.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden