• 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
figuring out if to-many is fault: _EOCheapCopyMutableArray
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

figuring out if to-many is fault: _EOCheapCopyMutableArray


  • Subject: figuring out if to-many is fault: _EOCheapCopyMutableArray
  • From: Jonathan Rochkind <email@hidden>
  • Date: Wed, 3 Mar 2004 14:25:41 -0600

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.


  • Follow-Ups:
    • Re: figuring out if to-many is fault: _EOCheapCopyMutableArray
      • From: Jonathan Rochkind <email@hidden>
  • Prev by Date: problem with WOForm, inserting an object into an array used to create the WOForm
  • Next by Date: Re: figuring out if to-many is fault: _EOCheapCopyMutableArray
  • Previous by thread: problem with WOForm, inserting an object into an array used to create the WOForm
  • Next by thread: Re: figuring out if to-many is fault: _EOCheapCopyMutableArray
  • Index(es):
    • Date
    • Thread