• 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: modeling problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: modeling problem


  • Subject: Re: modeling problem
  • From: Chuck Hill <email@hidden>
  • Date: Tue, 31 Mar 2009 15:41:34 -0700


On Mar 31, 2009, at 1:54 PM, Lachlan Deck wrote:

On 31/03/2009, at 8:16 AM, Chuck Hill wrote:

On Mar 30, 2009, at 1:58 PM, TW wrote:

On Mar 30, 2009, at 1:18 PM, Chuck Hill wrote:

On Mar 29, 2009, at 4:48 PM, TW wrote:

I have a model of our ldap directory with InetOrgPerson the base "user" entity. I've made InetOrgPerson abstract with it's table inetOrgPerson. I have the framework project containing that model in the build path of another that I'm using as a "generic user" framework.

In that second framework I have another model with a "GenericUser" entity. That entity has "InetOrgPerson" as it's parent. I've added this second framework to my app build path.

- in Entity Modeler if I set the table for "GenericUser" to "inetOrgPerson" (the same as it's parent), my app fetches 2 identical GenericUser EO's for each 1 matching record in LDAP

That is because you have set up Single Table Inheritance BUT not added any restricting qualifier on either entity. Are you certain that InetOrgPerson is marked as abstract? Check it again...

InetOrgPerson is definitely checked "Abstract" in my OD model.

I have never tried this without a restricting qualifier on one of them.


You could try adding a restricting qualifier of (1 = 0) on InetOrgPerson.

I didn't think I needed a restricting qualifier if the parent was abstract. I do get errors requiring a restricting qualifier if InetOrgPerson is _not_ abstract.

This sounds like a bug to me right now, please* bugreport.apple.com

That sounds right though. i.e., if you're fetching on the super entity (with deep fetch being true) it needs to know how to distinguish whether each record fetched is a parent node or not I would have thought.

If it is abstract, it should not be fetching them and creating 2 identical GenericUser EO's.



Chuck


-- Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific 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: 
 >modeling problem (From: TW <email@hidden>)
 >Re: modeling problem (From: Chuck Hill <email@hidden>)
 >Re: modeling problem (From: TW <email@hidden>)
 >Re: modeling problem (From: Chuck Hill <email@hidden>)
 >Re: modeling problem (From: Lachlan Deck <email@hidden>)

  • Prev by Date: Re: modeling problem
  • Next by Date: Re: Displaying Local Time on a Web Client
  • Previous by thread: Re: modeling problem
  • Next by thread: Re: modeling problem
  • Index(es):
    • Date
    • Thread