I've been trying to track down a bug and it *seems* that it might be
CoreData's fault (I highly doubt it but there's a small chance). I
have the following configuration:
- A base class, let's call it Base
- A subclass of Base, let's call it Subclass
Subclass has a to-many relationship to Base. Here's what I'm
observing:
- On startup, the to-many relationship is not restored (only in some
reproducible cases).
Are all the objects correctly marked inserted or updated before you
save ? Do all the objects report the correct inverses ?
If you change relationships with setPrimitiveValue:forKey: or on MOs
that haven't been inserted into a MOC or try to wire up relationships
in -awakeFromFetch, then things can go awry.
Do you have multiple MOCs saving ? The XML store is atomic, so the
last writer wins. The SQLite store merges changes from other saves.
Can you reproduce this in a new sample project ?
- Ben
_______________________________________________
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
