Are you sure the relationship's being called on the right object? If it's the result of a to-one relationship that doesn't exist, it could be an automatically created "phantom" object.
In the case of cascading popups, I typically initialize all levels in appendFromResponse if they're null. For instance, to set the selection on the top level, I'll get all the possibilities for the list, then grab the top one and make it the selection for the pop-up. At the same time I do that, I'll populate the next level also, getting the relationship result from the default object, and selecting the first from there… That way, you start with populated values... On Aug 22, 2011, at 11:13 AM, Michael Gargano wrote: > Just the default constructor, which implicitly calls super. All the model > classes are EOGenerated. Any other ideas to check? > > Thanks. > -Mike > > > On Aug 19, 2011, at 3:39 PM, Chuck Hill wrote: > >> Sounds like you forgot to call super someplace in your EOs. >> >> >> On 2011-08-19, at 12:27 PM, Michael Gargano wrote: >> >>> Hi all, >>> >>> I have cascading popup buttons that are narrowing down to a particular >>> instance of an entity and one of the popups is populated with the field >>> from a relationship on that entity. >>> So, the fetch spec. has a qualifier consisting of the values of all the >>> previous choices and it retrieves the narrowed set of objects. Next, I >>> iterate through the results adding the object from the relationship to a >>> NSMutableArray for display. It is at this point that, periodically, the >>> relationship returns null instead of the object. This is a test system so >>> there is only one entity in the database and this relationship should >>> definitely return an item. If I do this in reverse... I preform the fetch >>> on the relationship's entity and use key paths in the qualifier back to the >>> master entity it seems to go away (this is hideous). >>> >>> >>> So, to sum it up... even though the fetch returns the correct results, it >>> seems the proxy load of the relationship slave entity sometimes fails. >>> This is on a PostgreSQL DB, btw. >>> >>> Has anyone ever seen issues when faulting objects from a relationship? Is >>> it not guaranteed to return an object even if the inner join is definitely >>> valid? >>> >>> >>> Thanks. >>> -Mike >>> >>> _______________________________________________ >>> 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/chill%40global-village.net >>> >>> This email sent to [email protected] >> >> -- >> 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 protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/kenlists%40anderhome.com > > 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]
