I've got another CoreData problem, and this one is quite strange.
In this case, I have an entity that subclasses an abstract entity, and
for some very strange reason I cannot diagnose, it will only save
managed objects in that entity if the properties have very specific
values in them.
Now, I know what you're thinking, but yes, I am validating the objects
before inserting them, and they pass the validation, and the object is
returned by -insertedObjects prior to the save, and saving does not
cause the NSManagedObjectContext to return an error. The save goes
absolutely perfectly, except that the objects aren't actually saved.
The objects have zero constraints, except that all properties must be
set (and they are; I checked).
I already tried:
* changing the backing store from SQLite to XML; the same thing happened
* setting and changing constraints on some of the properties; nothing
changed, although setting one to be too narrow for its normal range
did generate expected validation errors
* changing the property names; didn't make a difference
* running the app with or without GC; non
* running the app as either X86 or X86-64; not that either
* running the app with the command line option -
com.apple.CoreData.SQLDebug 3, and sure enough, despite the records
validating and the MOC returning no errors upon save, no INSERT INTO
command is issued to sqlite except for the handful of records with
very specific values in them
What do I do now? (And I'm hoping I get an "are you sure it's plugged
in?"-type answer that turns out to be correct...)
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
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
