Details
-
Technical task
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.2(EOL)
-
None
-
GNU/Linux
Description
Now this starts to smell.
If a column is defined as NULL-able, 10.2 will automatically append DEFAULT NULL to create statements.
10.2
`description` text COLLATE utf8_bin DEFAULT NULL
|
10.0
`description` text COLLATE utf8_bin
|
Originally the column does not have DEFAULT value set at all!
Basically table exported from 10.2 will not work in a same way on MariaDB 10.0 or MySQL servers.
Attachments
Issue Links
- relates to
-
MDEV-15519 CHECKSUM TABLE gives different results across MariaDB 10.0 and 10.2
- Confirmed
-
MDEV-15377 10.2+ Integer DEFAULT values missing quotes
- Closed
-
MDEV-15390 information_schema returns quoted strings for default textual columns
- Closed
-
MDEV-15394 DEFAULT current_timestamp() discrepancy
- Closed
Furthermore, this only seems to apply for text columns which are defined NULL-able, while NOT-NULL-able text columns and varchar columns share same behavior with 10.0 series.
Same on both 10.2 and 10.0
author varchar(100) CHARACTER SET utf8 DEFAULT NULL
Same on both 10.2 and 10.0
article text CHARACTER SET utf8 NOT NULL
Now that's a mess.