Hi, Alexander!
I think it's a bug that needs to be fixed.
On Apr 11, Alexander Barkov wrote:
> Hi Sanja, and Igor,
>
> I noticed a FOR UPDATE behavior change in 10.3-MDEV-11953
>
> In 10.3 I run this script in a client session:
>
> CREATE OR REPLACE TABLE t1 (a INT NOT NULL PRIMARY KEY);
> CRE
On 04/12/2018 09:11 AM, Alexander Barkov wrote:
>>
>>>
>>> Anyway you can't use anymore:
>>> SELECT c FROM t1 ORDER BY a
>>> UNION
>>> SELECT c FROM t2 ORDER BY b
>>> ORDER BY c.
>>>
>>> You have to put it so:
>>> (SELECT c FROM t1 ORDER BY a)
>>> UNION
>>> (SELECT c FROM t2 ORDER BY b)
>>> ORDE
This is Muhammad Rashid from Karachi, Pakistan. I need some help to
implement MariaDB Master/Master replication with gtid on Microsoft azure
environment.
Although I have configured the implementation across azure "East US" and
"West 2 US" region using vm size "Standard E8s v3 (8 vcpus, 64 GB memory
Hi,
On 04/12/2018 07:59 AM, Alexander Barkov wrote:
> Hi Igor,
>
> Please do "reply all" when replying.
>
> On 04/12/2018 01:28 AM, Igor Babaev wrote:
>> Alexander,
>>
>> If you have the same behaviour you have to use
>>
>> SELECT * FROM t1 UNION (SELECT * FROM t2 FOR UPDATE).
>
> Thanks. This
Hi Igor,
Please do "reply all" when replying.
On 04/12/2018 01:28 AM, Igor Babaev wrote:
> Alexander,
>
> If you have the same behaviour you have to use
>
> SELECT * FROM t1 UNION (SELECT * FROM t2 FOR UPDATE).
Thanks. This worked fine for me.
>
> Otherwise it's considered as
>
> (SELECT *
5 matches
Mail list logo
