Re: EOModeling Addresses.... better design
Re: EOModeling Addresses.... better design
- Subject: Re: EOModeling Addresses.... better design
- From: Erwin <email@hidden>
- Date: Wed, 8 Dec 2004 18:20:50 +0100
That's what I mean ... on a design side, is it better that a specific
attribute ?
Erwin
Le Dec 8, 2004, à 6:14 PM, Chuck Hill a écrit :
Do you mean
customer ->> addresses
customer -> defaultAddress
Where defaultAdress is in the list of addresses? This works, I use
it. Just make sure that the two relationship are always kept updated
when things change.
Chuck
On Dec 8, 2004, at 8:14 AM, Erwin wrote:
not a DBmodeler expert :
I am modeling Address entity for a Customer entity (one-to many)
(delivering, billing, home, office,..)
I defined a default address using an addressType attribute in the
Address entity
but
should it be better (if possible,) to define in EOModeler a specific
one-to-one relationship (defaultAddress) ??
I heard that modeling addresses (should be simple !) seems to be a
little bit tricky....
Erwin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village.net
This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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