Hi, i would do it that way and handle modifications manually. So if the user modifies the address, just create a copy+changes and assign it to the user.
Hope it helps, Bjoern -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gustavo Pizano Sent: Monday, November 16, 2009 12:23 PM To: WebObjects-Dev Apple Subject: Little help with a Db design quesiton Hello all. I know this is off topic, but you guys have helped me in the past with such a questions, so I hope Im not bothering anybody. Im building a Invoicing app, so I have my EOModel and this is what I have. Person: Client: Parent is Person User: Parent is Person. Person < >> Address (toAddress) Invoice << > User (toUser) Invoice<< > Client (toClient) InvoiceItem<< >> Invoice InvoiceStatus< >> Invoice now... what happens if the Person changes address?, it will change the address of all already created invoices, which for record purposes its not allowed, it think. (I mean my already created invoices should stay as they where created) So is it correct to add a relation from Invoice << > Address ?, so when I add a new address to Person the invoice will kept the old address. right? how can I avoid when modifying the address, if I do this, then the invoice toAddress will change also. Thanks G. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/bw%40condat.de This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
