On 2016-04-19, 2:01 PM, "OC" wrote:
>Chuck,
>
>On 19. 4. 2016, at 22:48, Chuck Hill wrote:
>
> (b) contrariwise, with WOAllowsConcurrentRequestHandling = YES, two R/R
> loops can be processed at the same time. Which might cause one of them
> save changes, and in a couple of mi
Chuck,
On 19. 4. 2016, at 22:48, Chuck Hill wrote:
(b) contrariwise, with WOAllowsConcurrentRequestHandling = YES, two R/R
loops can be processed at the same time. Which might cause one of them
save changes, and in a couple of milliseconds another save its changes
based on
On 2016-04-19, 1:43 PM, "OC" wrote:
>Chuck,
>
>On 19. 4. 2016, at 22:30, Chuck Hill wrote:
>
>>> (b) contrariwise, with WOAllowsConcurrentRequestHandling = YES, two R/R
>>> loops can be processed at the same time. Which might cause one of them save
>>> changes, and in a couple of millisecond
Chuck,
On 19. 4. 2016, at 22:30, Chuck Hill wrote:
>> (b) contrariwise, with WOAllowsConcurrentRequestHandling = YES, two R/R
>> loops can be processed at the same time. Which might cause one of them save
>> changes, and in a couple of milliseconds another save its changes based on a
>> diffe
Hi,
On 2016-04-19, 1:03 PM, "OC" wrote:
>On 19. 4. 2016, at 20:06, Chuck Hill wrote:
>
... 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 ext
Chuck,
On 19. 4. 2016, at 20:06, Chuck Hill wrote:
>>> ... 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 OS
Hi,
On 2016-04-19, 7:09 AM,
"webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of OC"
wrote:
>Samuel,
>
>On 19. 4. 2016, at 15:49, Samuel Pelletier wrote:
>
>> WOAllowsConcurrentRequestHandling=NO or YES does not have impact on this
>> subject, only the number of live Obj
OC,
I always tough the propagation was done by the OSC after the commit and
snapshot refresh because this is when there is something to propagate but I
never checked the code.
Probably Chuck, the wonderpedia, can tell us.
Samuel
> Le 19 avr. 2016 à 10:09, OC a écrit :
>
> Samuel,
>
> On
Just a quick question...
ERMailDataAttachment says “The mime type is pulled from the file name”. I
happen to know the mime type; is there a way to set it explicitly? The
filename, contrariwise, is set by user and I have a little control over it; if
he wants to name a JPEG “foo.pdf“, I should le
Hi Paul,
That’s probably something that doesn’t live in your zones array, so
zonesWithRawOffset is returning an empty array of which lastObject returns
null, and thus the null pointer exception. Without knowing the zone string
causing the problem, it’s a tough one. I’d probably start by logging
Samuel,
On 19. 4. 2016, at 15:49, Samuel Pelletier wrote:
> 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
>
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
I’ve been trying to implement the ERAttachment Package for weeks and seems
‘absolutely’ impossible!! I get these two Exceptions in the same cycle [Data
Entry & Update/Retrieval].. wow? Anyone familiar with this problem? HELP
[A]
[2016-4-19 9:5:35 EDT] java.util.NoSuchElementException: There
... 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
14 matches
Mail list logo
