Re: [OT] Design Question : People getting married
Re: [OT] Design Question : People getting married
- Subject: Re: [OT] Design Question : People getting married
- From: MacFirst <email@hidden>
- Date: Thu, 24 Feb 2005 16:22:07 -0800
on 2/23/05 10:30 PM, John Kestner <email@hidden> went on and on saying,
in part:
> 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.
Or, if you're interested in knowing the person's name at the time of
publication, and their current name, and other aliases under which they have
published, perhaps you have an author record, which is <->> with a name
record, which is <<->> with the publication. That way, each publication is
authored by some number of authors, each under 1 name (for that
publication), but you can X-ref all around.
_______________________________________________
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