[MDEV-29770] Broken table cannot be CREATE OR REPLACE -ed anymore Created: 2022-10-11 Updated: 2023-05-18 Resolved: 2023-01-26 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Create Table |
| Affects Version/s: | N/A |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Critical |
| Reporter: | Elena Stepanova | Assignee: | Aleksey Midenkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
When CREATE OR REPLACE was working as DROP + CREATE, even a hopelessly damaged table could be CREATE OR REPLACE -ed, because it could be dropped (with a warning). It is no longer the case, now CREATE OR REPLACE fails on such tables, and an explicit DROP is required instead. Maybe it's an unavoidable limitation or even an intentional change, but taking into account usual preferences of the reviewer, it has to be clarified.
After MDEV-25292:
Before MDEV-25292:
|
| Comments |
| Comment by Aleksey Midenkov [ 2022-10-17 ] |
|
Please review bb-10.11-midenok |