Re: Problem saving in a Core Data application
Re: Problem saving in a Core Data application
- Subject: Re: Problem saving in a Core Data application
- From: Jerry Krinock <email@hidden>
- Date: Sat, 13 Nov 2010 18:34:52 -0800
On 2010 Nov 13, at 15:23, Kyle Sluder wrote:
> The only common race condition I can think of off the top of my head is the delay performing that NSController does.
Maybe that's it. I just remember that when I first started using Core Data, my first instinct was to uncheck those "Optional" boxes when a property was required. I frequently got "save" errors as described by Paul until I checked them back on. I vaguely remember debugging one case and found that Core Data was doing its validation before my business logic received the notification which triggered setting the non-optional property, or something like that. On another occasion, I tried implementing some of Core Data's built-in validation methods, assuming that they would give me some hooks to recover from the validation errors, but was disappointed to find that, instead, it just displayed these obnoxious error dialogs.
> I've avoided Core Data for anything more than toy apps (our apps had all moved off Core Data by the time I showed up).
Looks like we're having another Dump On Core Data Weekend. Let's try and clean this up before Monday morning, eh :)
_______________________________________________
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