Re: a HUGE Core Data bug
Re: a HUGE Core Data bug
- Subject: Re: a HUGE Core Data bug
- From: Aurélien Hugelé <email@hidden>
- Date: Mon, 12 Mar 2007 10:35:25 +0100
I think that your reactions guys are quite surprising. Saying that "I
didn't experience any problems either. Everything works as expected"
is a typical user answer, not a serious developer answer. We all
know, as developers, that sometimes bugs are difficult to reproduce,
and difficult to isolate. I've demonstrated a Core Data problem (that
is documented), so the problem exists, there is no reason to deny it.
Moreover, you seem to have overlooked the details: the problem only
arise with SQL store, not with the 2 other stores... so the behavior
of Core Data, regarding graph coherency, is not consistent and
depends on the store type. This is what I call a major drawback:
performance by type of store are well commented, but the coherency is
not...
If adding an inverse relationship is a compulsory for Core Data, then
i'll file a bug to make Xcode not only warn me when there is no
inverse, but generate a compiler error by default (and generate a
warning only if the developer set the right parameter...)
And please try my program both on Mac OS X 10.5 and 10.4, the
behavior is definitely not the same, so I think that Core Data
engineers have probably found a way to enhance relationships without
inverses integrity.
On 9 mars 07, at 16:31, Aurélien Hugelé wrote:
Hi list!
I just want to stress Core Data users, since i've discovered what I
think is a huge bug, that I reported to apple.
Basically, save an object graph to a SQL store, reload it from
disk, the object graph is not restored correctly, some
relationships are missing.
You can download a very simple project that demonstrate the bug at
http://developer.gumitech.com/CoreDataDramaticalBug.zip
A Readme is included that explains the details.
I'm quite surprised that nobody here has encountered this bug, but
honestly I can't trust Core Data anymore, and I fear a customer
complain about data loss.
Just an optimist note, the bug can't be reproduced on Mac OS X
10.5... But IMHO Apple must fix it on 10.4 too.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
40gumitech.com
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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