Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Description
Oracle addressed Bug #27542720 SCHEMA MISMATCH - TABLE FLAGS DON'T MATCH, BUT FLAGS ARE NUMBERS in a peculiar way: replacing exact diagnostic output with less exact one.
Yes, hexadecimal flags may be user-friendly, but they may be crucial in diagnosing an issue. Adding more information (such as this) would be better:
ERROR HY000: Schema mismatch (Table flags don't match, server table has 0x23 and the meta-data file has 0x29; .cfg file uses ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=8)
|
Attachments
Issue Links
- blocks
-
MDEV-16850 Merge new release of InnoDB 5.7.23 to 10.2
-
- Closed
-
- relates to
-
MDEV-15049 Importing InnoDB table from 10.1 to 10.2 causes Schema mismatch (Expected FSP_SPACE_FLAGS=0x21, .ibd file contains 0x0
-
- Closed
-
-
MDEV-20930 Document that SHOW CREATE TABLE on InnoDB tables only shows ROW_FORMAT when explicitly set
-
- Closed
-
-
MDEV-20974 Don't require .cfg files to import InnoDB tablespaces
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue blocks |
issue.field.resolutiondate | 2018-07-30 11:13:58.0 | 2018-07-30 11:13:58.68 |
Fix Version/s | 10.1.35 [ 23116 ] | |
Fix Version/s | 10.2.17 [ 23111 ] | |
Fix Version/s | 10.3.9 [ 23114 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Link |
This issue relates to |
Link |
This issue relates to |
Link |
This issue relates to |
Workflow | MariaDB v3 [ 88641 ] | MariaDB v4 [ 154728 ] |