Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.11, 11.4, 11.8, 12.3, 13.1, 10.11.19
-
Official MariaDB Docker images mariadb:10.11.18 and mariadb:10.11.19, running Linux amd64 containers under Docker Desktop 4.97.0 on Windows.
Server-reported versions:
10.11.18-MariaDB-ubu2204 — works
10.11.19-MariaDB-ubu2204 — fails
Storage engine: MyISAM
Character set/collation: utf8mb3 / utf8mb3_unicode_ciOfficial MariaDB Docker images mariadb:10.11.18 and mariadb:10.11.19, running Linux amd64 containers under Docker Desktop 4.97.0 on Windows. Server-reported versions: 10.11.18-MariaDB-ubu2204 — works 10.11.19-MariaDB-ubu2204 — fails Storage engine: MyISAM Character set/collation: utf8mb3 / utf8mb3_unicode_ci
Description
MariaDB 10.11.19 rejects a MyISAM table definition that works on 10.11.18. This affects both CREATE TABLE and opening existing table files created by 10.11.18.
Minimal reproduction
CREATE TABLE minimal_interleaved ( |
a INT, |
z CHAR(0) GENERATED ALWAYS AS (NULL) VIRTUAL, |
b INT, |
v INT GENERATED ALWAYS AS (a) VIRTUAL |
) ENGINE=MyISAM
|
DEFAULT CHARSET=utf8mb3 |
COLLATE=utf8mb3_unicode_ci; |
Expected result
The table is created successfully, as on 10.11.18.
Actual result on 10.11.19
CREATE TABLE fails with:
ERROR 1033 (HY000): Incorrect information in file: './native19/minimal_interleaved.frm'
|
Subsequent queries return ERROR 1146 because the failed CREATE does not leave an accessible table.
Possible connection to MDEV-40571
MDEV-40571 introduced additional .frm field-layout validation in 10.11.19. The interaction between an interleaved zero-length virtual column and a later nonzero-length virtual column appears relevant.
Attachments
Issue Links
- is caused by
-
MDEV-40571 insufficient validation of frm data when opening a table
-
- Closed
-