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 12:31:08 -0800
On 2010 Nov 13, at 11:29, Paul Johnson wrote:
> <The document "xxx" could not be saved. selectedType is a required value.
Oh, that's good because this error message is much easier to deal with than the one in your original post.
Apparently, in you data model you have un-checked the 'Optional' box for the property 'selectedType', and either the value has not been set, or, more likely, it's being set a few microseconds *after* Core Data checks for it and barfs, and the error is therefore a false alarm.
My advice is: Never un-check any of those 'optional' boxes in a data model. Besides checking too early, these checkboxes, and other validation methods built into Core Data, present incomprehensible and embarrassing error dialogs like that. They are OK for in-house work, but not for a finished product. Instead, implement business logic and design your user interface so that it is not possible to enter invalid data. In cases where you can't avoid validation, write your own code to detect and recover appropriately.
_______________________________________________
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