Atomic CREATE OR REPLACE TABLE
(MDEV-25292)
|
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Technical task | Priority: | Critical |
| Reporter: | Aleksey Midenkov | Assignee: | Marko Mäkelä |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
"InnoDB changes" article has been added to the main task commit. Any of the branches can be reviewed: |
| Comments |
| Comment by Marko Mäkelä [ 2022-06-13 ] |
|
I think that the design questions and suggestions in MDEV-25292 must be addressed before this can be reviewed. |
| Comment by Marko Mäkelä [ 2022-06-21 ] |
|
I "reviewed" the changes by submitting my own versions of the InnoDB changes. There was apparently no need to remove the assertion ut_ad(err != DB_DUPLICATE_KEY) from row_rename_table_for_mysql(). |