Hello,
After research and reflection I decided to remove some
troublesome inverse relationships from the Core Data model in my
multi-machine application. I've taken steps to avoid database
integrity issues and have written accessors to preserve the data
embodied in the removed relationships.
It has brought a small performance increase (especially on
refreshing from database) and reduced optimistic locking and
'cannot remove observer' exceptions.
The hitch is the 30-odd, triply redundant, build warnings re:
1. not having inverse relationships
2. No Action delete rules.
I respect warnings but is there a way to placate the build
system on one or both of these specific issues? Or to suppress
the warnings? Then, I can more easily spot acute warnings.
Cheers,
Steve
ps. lets take off-line any chats about warning and inverse
relationship merit.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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 arch...@mail-archive.com
