CoreData Bug? (SQLite vs XML)
CoreData Bug? (SQLite vs XML)
- Subject: CoreData Bug? (SQLite vs XML)
- From: Milen Dzhumerov <email@hidden>
- Date: Sun, 13 Sep 2009 17:14:53 +0100
Hi all,
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).
To see what's going on behind the scenes, I logged some information
using the following snippet:
-(void)awakeFromFetch
{
for(id base in [self relationship])
Log(@"%@", base);
...
}
One of the reproducible cases involves creating 3 instances of
Subclass and 2 instances of Base. After a relaunch, only 1 instance of
Subclass gets restored properly, the other 2 don't restore the
relationship properly. When I use SQLite, nothing gets printed from -
awakeFromFetch. If I switch to XML, everything works perfectly. This
bug is a showstopper for us and I don't want to use XML as it's
noticeably slower when we test our app.
I'm not sure how to go about this problem as it seems like a bug in CD
(I can't find a better explanation why it happens only when using
SQLite and not XML). Any pointers / hints on what I can do to track
this down are greatly appreciated.
M
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden