Re: Docs about "twinned" process and pre-emptive mode

Ok, I dug out an old laptop which had a lot of interesting discussion on this from 2011. What I’m wondering is if triggers can now run pre-emptively (if they are compliant code-ways: no IP variables etc). In 2011, David Dancy said that any regular 4D code whatsoever would force the method to

Re: Docs about "twinned" process and pre-emptive mode

> On 19 Jan 2018, at 04:10, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > are you familiar with the request log file? > > you will see a P (for preemptive) or C (for cooperative) indicated for each > network request. The log file seems to do this for everything *except* the

Re: Docs about "twinned" process and pre-emptive mode

Thanks Miyako. That’s useful. I basically was wanting to know if inline SQL used the “twinned” pre-emptive thread or not. Peter > On 19 Jan 2018, at 04:10, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > are you familiar with the request log file? > > you will see a P (for

Re: Docs about "twinned" process and pre-emptive mode

Hello, focusing on commands or syntax may lead you in the wrong direction, as there are so many possibilities in SQL and QUERY. are you familiar with the request log file? you will see a P (for preemptive) or C (for cooperative) indicated for each network request.

Docs about "twinned" process and pre-emptive mode

Hi I’ve been raking through the online documentation trying to find where the querying modes pre-emptive / co-operative are documented but have been unsuccessful. What I’m specifically looking for is more background on what conditions SQL queries use the twinned pre-emptive process for