On Nov 19, 2009, at 10:19 PM, Greg Hoover wrote:
> I've been working through adding scriptability to my CoreData application but
> ran into a snag: accessing relationships may return a fault instead of the
> actual set of objects. Is there an "accepted" way of solving this issue? I
> don't wa
I've been working through adding scriptability to my CoreData application but
ran into a snag: accessing relationships may return a fault instead of the
actual set of objects. Is there an "accepted" way of solving this issue? I
don't want the accessor to "always" fault the objects in, just whe
