Re: EOFetchSpecification prefetching and Multiple EOModels
Re: EOFetchSpecification prefetching and Multiple EOModels
- Subject: Re: EOFetchSpecification prefetching and Multiple EOModels
- From: Chuck Hill <email@hidden>
- Date: Wed, 11 Mar 2009 10:20:33 -0700
On Mar 11, 2009, at 9:46 AM, David Avendasora wrote:
Hi all,
I've run into something that I haven't been able to find documented
anywhere, but does seem to fit with other Cross-Model relationship
issues (http://lists.apple.com/archives/Webobjects-dev/2008/Dec/msg00058.html
).
If you have a cross-model relationship,
Same database or different database?
you can't prefetch the relationship when constructing an
EOFetchSpecification. It will simply return null, or an empty
NSArray if it is a to-many relationship.
I think that would be a bug. Prefetching is a separate select so it
should not matter if it is in a different database.
Subsequent calls to the relationship simply return null or the empty
NSArray.
Which is clearly a bug if they return proper results normally.
Is this the expected behavior?
No to me.
It seems logical, but unexpected to me (Yes, those two concepts can
coexist simultaneously in my brain).
I don't find that surprising in the least! ;-)
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