Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Description
Traditionally, DROP TABLE and TRUNCATE TABLE discarded any locks that may have been held on the table. This feels like an ACID violation. Probably most occurrences of it were prevented by meta-data locks (MDL) which were introduced in MySQL 5.5.
It is cleaner to always protect DDL operations with an exclusive table lock. Other operations are doing this in MariaDB 10.3, but not TRUNCATE TABLE.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| issue.field.resolutiondate | 2018-01-25 21:50:36.0 | 2018-01-25 21:50:36.027 |
| Fix Version/s | 10.3.5 [ 22905 ] | |
| Fix Version/s | 10.3 [ 22126 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 85126 ] | MariaDB v4 [ 153642 ] |