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: Paul Johnson <email@hidden>
- Date: Sat, 13 Nov 2010 15:52:58 -0600
Yes, I should have included my own program as it all has to work together.
Still, it makes the "Optional" switch rather useless, if you ask me. Perhaps
there is a way to introduce some synchronization that I'm not aware of.
On Sat, Nov 13, 2010 at 3:34 PM, Jerry Krinock <email@hidden> wrote:
>
> On 2010 Nov 13, at 13:24, Paul Johnson wrote:
>
> > So, what I understand is that there are some "race conditions" within
> Core Data that make it impossible to specify that a property be required and
> that it is necessary to include in one's code any checks for the presence of
> values.
>
> No; the race conditions are in the interaction between the business logic,
> bindings, etc. in your design and Core Data.
>
>
_______________________________________________
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