Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Duplicate
-
10.2.14
-
None
-
Windows
Description
Hello Team,
We will be upgrading from existing "10.0.20" to "10.2.14-MariaDB-log" on Production running on linux.
But before this I was testing "10.2.14-MariaDB-log" on my local machine on Windows and I came across a use case which includes adding 2 columns (With new feature of default value as SQL expressions) and 1 check constraint including those two new columns, on a table consists of only 1 dummy record.
And soon after that when I dropped those 2 columns along with constraint, I mistakenly misspelled constraint name, which results in the 1 record of table become corrupt.
So please find attached the exact commands which caused by 1 record of my table become corrupt and kindly confirm the bug.
Attachments
Issue Links
- is duplicated by
-
MDEV-15338 Assertion `!table || (!table->read_set || bitmap_is_set(table->read_set, field_index))' failed on dropping column with CHECK
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Alice Sherepa [ alice ] |
Link |
This issue is duplicated by |
issue.field.resolutiondate | 2018-06-22 13:56:52.0 | 2018-06-22 13:56:52.661 |
Fix Version/s | 10.2.16 [ 23110 ] | |
Fix Version/s | 10.3.8 [ 23113 ] | |
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 87992 ] | MariaDB v4 [ 154552 ] |
Thanks for the report!
I reproduced it on MariaDB 10.2.14, it looks like it is the same problem as
MDEV-15338, that was fixed by commit 2dff8fe.