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: Kyle Sluder <email@hidden>
- Date: Sat, 13 Nov 2010 15:23:54 -0800
On Nov 13, 2010, at 1: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.
The only common race condition I can think of off the top of my head is the delay performing that NSController does. Is there more that I'm not aware of? 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).
--Kyle Sluder_______________________________________________
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