maria-developers team mailing list archive
-
maria-developers team
-
Mailing list archive
-
Message #05580
Re: unexpected "Duplicate entry" error
Hi!
>>>>> "Vincent" == Vincent Pelletier <vincent@xxxxxxxxxx> writes:
Vincent> Hi.
Vincent> Bumping this thread with a slightly different finding which may help
Vincent> understanding the issue.
Vincent> I'll use two command lines for this test, "MariaDB 1" and "MariaDB 2",
Vincent> also distinguished by indentation level for readability.
Vincent> Server version: 5.5.30-MariaDB-log MariaDB Server
<cut>
Vincent> So far, all good.
Vincent> MariaDB 1> delete from tst;
Vincent> Query OK, 3 rows affected (0.00 sec)
Vincent> Why "3 rows affected" ?
This is because in InnoDB, delete is run under the READ COMMITTED
isolation level, not REPETABLE READ as SELECT.
This is an optimization that Heikki did a long time ago that has this
strange side effect.
See the comment posted by Radek on
http://dev.mysql.com/doc/refman/5.5/en/delete.html
Regards,
Monty
Follow ups
References
-
unexpected "Duplicate entry" error
From: Kazuhiko Shiozaki, 2013-02-18
-
Re: unexpected "Duplicate entry" error
From: Kristian Nielsen, 2013-02-18
-
Re: unexpected "Duplicate entry" error
From: Kazuhiko Shiozaki, 2013-02-18
-
Re: unexpected "Duplicate entry" error
From: Kazuhiko Shiozaki, 2013-02-18
-
Re: unexpected "Duplicate entry" error
From: Kristian Nielsen, 2013-02-18
-
Re: unexpected "Duplicate entry" error
From: Kazuhiko Shiozaki, 2013-02-18
-
Re: unexpected "Duplicate entry" error
From: Kazuhiko Shiozaki, 2013-02-20
-
Re: unexpected "Duplicate entry" error
From: Kristian Nielsen, 2013-02-21
-
Re: unexpected "Duplicate entry" error
From: Kazuhiko Shiozaki, 2013-02-26
-
Re: unexpected "Duplicate entry" error
From: Vincent Pelletier, 2013-05-21