Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.1.19, 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL)
-
None
Description
If I add backspaces, a literal 0x00, or other unusual characters to an enum value, I can see very strange results:
MariaDB [test]> select version();
|
+-----------------+
|
| version() |
|
+-----------------+
|
| 10.1.19-MariaDB |
|
+-----------------+
|
1 row in set (0.00 sec)
|
|
|
MariaDB [test]> create table t1(id int, e enum('foo', 'bar', 0x08080808080808, 'whiz', 'bang', 0x00, 'hello') NOT NULL) engine=innodb;
|
Query OK, 0 rows affected (0.25 sec)
|
|
|
MariaDB [test]> show create table t1\G
|
*************************** 1. row ***************************
|
Table: t1
|
Create Table: CREATE TABLE `t1` (
|
`id` int(11) DEFAULT NULL,
|
`e` enum('foo',','whiz','bang') NOT NULL
|
) ENGINE=InnoDB DEFAULT CHARSET=latin1
|
1 row in set (0.00 sec)
|
|
|
MariaDB [test]> describe t1\G
|
*************************** 1. row ***************************
|
Field: id
|
Type: int(11)
|
Null: YES
|
Key:
|
Default: NULL
|
Extra:
|
*************************** 2. row ***************************
|
Field: e
|
Type: enum('foo',','whiz','bang')
|
Null: NO
|
Key:
|
Default: NULL
|
Extra:
|
2 rows in set (0.00 sec)
|
I can only imagine it gets worse if I add FormFeed or NewLine charaters. Also I am concerned how this impacts dump-and-restore.