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 want the accessor to "always" fault the objects in, just when they're
> being accessed from AppleScript. Is creating another accessor the proper way
> to get around this?
Can you be more specific about the problem you are having and what specifically
you are trying to do?
In particular, I’m not sure what you mean by:
I don't want the accessor to "always" fault the objects in, ust when
they’re being accessed from AppleScript.
Unless you prefetch relationships, they will be a fault. (If you need to know,
you can test this with -hasFaultForRelationshipNamed:. If you need to access
the related objects though, you need to fire the fault.
- Jim
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
