• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: EOModeling Addresses.... better design
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOModeling Addresses.... better design


  • Subject: Re: EOModeling Addresses.... better design
  • From: Chuck Hill <email@hidden>
  • Date: Mon, 13 Dec 2004 09:14:02 -0800

Cleaning out the inbox...

Yes, I think so. It more closely models "Each customer has a default address. A customer may have many addresses". Of course, you can describe it as "A customer may have many addresses, one of which is their default address". To me, it appears that "default address" is more a property of a customer than "default" is the poperty of an address. When I have used this design, I found the code more natural as well.

Chuck


On Dec 8, 2004, at 9:20 AM, Erwin wrote:

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:
email@hidden


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









--
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


References: 
 >EOModeling Addresses.... better design (From: Erwin <email@hidden>)
 >Re: EOModeling Addresses.... better design (From: Chuck Hill <email@hidden>)
 >Re: EOModeling Addresses.... better design (From: Erwin <email@hidden>)

  • Prev by Date: Re: date comparison in EOModeler
  • Next by Date: Re: EOF and Stored Procedure in MS-SQL
  • Previous by thread: Re: EOModeling Addresses.... better design
  • Next by thread: Current builds available
  • Index(es):
    • Date
    • Thread