Re: figuring out if to-many is fault: _EOCheapCopyMutableArray
Re: figuring out if to-many is fault: _EOCheapCopyMutableArray
- Subject: Re: figuring out if to-many is fault: _EOCheapCopyMutableArray
- From: Jonathan Rochkind <email@hidden>
- Date: Wed, 3 Mar 2004 14:47:17 -0600
Nevermind. _EOCheapCopyMutableArray does indeed implement EOFaulting.
A typo bug of mine was confusing me.
At 2:25 PM -0600 3/3/04, Jonathan Rochkind wrote:
I've got a bunch of objects, with to-many relationships. I want to
figure out if those to-many relationships are still to-many faults,
or if they've been cleared. So I can batch fetch the relationship,
but only if neccesary for efficiency---if the to-many faults have
already been cleared, I don't want to batch fetch.
But how do I figure this out? I know I _could_ class-cast to
_EOCheapCopyMutableArray, and call isFault() on it. But isn't there
a way to do this without using undocumented API? Why doesn't
_EOCheapCopyMutableArray implement EOFaulting? Then I could just do:
if (object.relationship() instanceof EOFaulting &&
((EOFaulting)object.relationship()).isFault()).
But it doesn't seem to. So I can't. Is there really no way to do
this but rely upon undocumented API? (In this case, a whole
undocumented private-use class, _EOCheapCopyMutableArray).
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.