Re: CoreData Bug? (SQLite vs XML) + isolated reproducible case
Re: CoreData Bug? (SQLite vs XML) + isolated reproducible case
- Subject: Re: CoreData Bug? (SQLite vs XML) + isolated reproducible case
- From: Milen Dzhumerov <email@hidden>
- Date: Mon, 12 Oct 2009 21:46:18 +0100
Adding an inverse does solve the problem (maybe I missed mentioning
it). The reasons why I thought it was a CD bug are the following:
- I don't think it's obvious from the docs that the SQLite store can't
cope with relationships that have no inverses (I was told by Danny
Greg that having an inverse was rule #1).
- The code works fine with the XML / Atomic store (maybe I should be
treating that as a coincidence instead of the other way around).
- I can't remember exactly but I'm not quite sure the "this is an
advanced setting (no object can be in multiple destinations for a
specific relationship)" part appeared when I compiled under Leopard
with Xcode 3.1 (there's a high possibility that I might be wrong, I
don't Leopard around anymore to test).
Maybe I should start treating warnings as errors. In any case, thanks
a lot to everyone who took a look at the issue, especially Ben.
M
On 12 Oct 2009, at 21:33, Ben Trumbull wrote:
Thanks for the test project. However, reviewing and fixing all
compiler warnings is likely to make development a significantly less
frustrating experience. We've taken to fixing (nearly) all compiler
warnings, even ones we know are harmless, so we can easily find the
new ones that likely aren't. A lot of people like -Werror for
exactly this reason, but that's a bit too draconian for my taste.
CoreDataBug_DataModel.xcdatamodel:SmartFolder.sources: warning:
SmartFolder.sources -- to-many relationship does not have an inverse:
- Ben
_______________________________________________
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