• 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
Parallel structure EO modeling
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Parallel structure EO modeling


  • Subject: Parallel structure EO modeling
  • From: Ken Anderson <email@hidden>
  • Date: Tue, 26 Feb 2013 15:11:11 -0500

All,

I have a difficult decision to make and am waffling back and forth.  I'm hoping some of you guys might have come across a similar situation and would have some recommendations.

I have a model where a number of entities can by applied only to males or only to females (it's an exercise app).  Part of me wants to create sub-entities called "Male…" and "Female…" because EOF will effectively validate relationships for me.  Unfortunately, it's a pretty deep entity hierarchy and there would be a lot of entities that would have to fall into this category.  Not to mention there are join tables that wouldn't have an M/F flag, but to stay consistent would have to be subclassed as well.

Any thoughts?  I would do them all with single table inheritance, so there wouldn't be much of a performance hit.

Thanks,
Ken


 _______________________________________________
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


  • Follow-Ups:
    • Re: Parallel structure EO modeling
      • From: Ramsey Gurley <email@hidden>
  • Prev by Date: Re: ERModern and ERDControllerButton
  • Next by Date: Re: Parallel structure EO modeling
  • Previous by thread: Re: Hello World Project - Installation Development
  • Next by thread: Re: Parallel structure EO modeling
  • Index(es):
    • Date
    • Thread