Hi, Russell!
On Jan 30, Russell J.T. Dyer wrote:
> How about concurrent_assign ?
I think "concurrent" already has a clear meaning, at least in MariaDB -
operations are done "concurrently" if they're executed truly in
parallel, usually in different threads. For example, both MyISAM and
InnoDB
Hi, Ian!
On Jan 30, Ian Gilfillan wrote:
> simultaneous_assignment would be my choice; as you say it's the most
> accurate, if a little long.
Thanks. That's what I'll end up with, I suppose.
I preferred simultaneous_set, and even changed the code to use it,
but then I realized that "set" is a
simultaneous_assignment would be my choice; as you say it's the most
accurate, if a little long.
30/01/2018 13:24, Sergei Golubchik wrote:
Hi, Russell!
On Jan 29, Russell J.T. Dyer wrote:
Is this mode related only to UPDATE and this feature? If so, maybe it
could be something like one of
Hi, Russell!
On Jan 29, Russell J.T. Dyer wrote:
> Is this mode related only to UPDATE and this feature? If so, maybe it
> could be something like one of these:
>
> update_static
> update_stasis
> update_isolation
>
> These would focus on the fact that it's related just to UPDATE and that the
or 'concurrent_assign'/'concurrent assignment'
-- Peter
On Tue, Jan 30, 2018 at 11:35 AM, Peter Laursen
wrote:
> 'concurrent_eval'/'concurrent_evaluation'
>
> ?'?
>
>
> -- Peter
> -- Webyog
>
> On Mon, Jan 29, 2018 at 6:19 PM, Sergei Golubchik
>
Hi, Ian, Russell,
As you know, UPDATE in MariaDB is executed left-to-right, say, in the
case of
UPDATE t1 SET a=b, b=a
both columns will have the same value, old value of `b`. We're now
introducing a new sql_mode to have standard compatible behavior, where
all assignments are executed kind of
6 matches
Mail list logo