Re: just checking...
Re: just checking...
- Subject: Re: just checking...
- From: Samuel Pelletier <email@hidden>
- Date: Tue, 19 Apr 2016 09:49:46 -0400
Hi OC,
WOAllowsConcurrentRequestHandling=NO or YES does not have impact on this subject, only the number of live ObjectStoreCoordinator in the app matter.
If you do nat have any external access to the database and a single OSC, you are OK. Changes are propagated to others EOEditingContext under the same OSC during saveChanges, this is the magic part of EOF.
If a last modified win policy is OK for the updates, you can even disable them. The goal of the attributes used for locking is to detect an update collision, if you do not care about them, just disable de detection.
Regards,
Samuel
> Le 19 avr. 2016 à 09:09, OC <email@hidden> a écrit :
>
> ... whether I am overlooking something or not.
>
> I do think that in a single-instance application with WOAllowsConcurrentRequestHandling=NO and without background tasks is locking of any attribute but PK completely superfluous and can be switched off in the model without any adverse effect.
>
> Am I right? Or do I overlook some disaster scenario?
>
> Thanks,
> OC
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden