• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: a HUGE Core Data bug
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: a HUGE Core Data bug


  • Subject: Re: a HUGE Core Data bug
  • From: "I. Savant" <email@hidden>
  • Date: Fri, 9 Mar 2007 11:44:51 -0500

Aurélien:

To say, "... but honestly I can't trust Core Data anymore ..." is a bit alarmist, don't you think?

Should this be happening? No, obviously not, but then the documentation does warn that a relationship without an inverse is not recommended* and obeying it seems to fix the problem. I wouldn't call this a bug, I would expect "the unexpected" to happen in some cases by going against the recommendations of the documentation for the technology I'm using.

In your example, you noted that with an inverse relationship, the problem does not exist and that the documentation clearly states relationships without an inverse is not recommended. It's safe to assume this is one of the reasons why. The solution? Add an inverse relationship as recommended by the documentation ... problem solved.

--
I.S.

* Incidentally, that very premise is the basis for many restraining orders in the US, so the Courts apparently agree, but I digress ...




On Mar 9, 2007, at 10:31 AM, 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:
40gmail.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


  • Follow-Ups:
    • Re: a HUGE Core Data bug
      • From: email@hidden
References: 
 >a HUGE Core Data bug (From: Aurélien Hugelé <email@hidden>)

  • Prev by Date: Re: alloc init thread safe?
  • Next by Date: Re: Minimal cocoa application
  • Previous by thread: a HUGE Core Data bug
  • Next by thread: Re: a HUGE Core Data bug
  • Index(es):
    • Date
    • Thread