Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5, 10.3(EOL), 10.4(EOL)
-
None
Description
I run this script:
CREATE OR REPLACE TABLE t1 (a VARBINARY(10)) CHARACTER SET utf8 |
PARTITION BY LIST COLUMNS (a) (PARTITION p0 VALUES IN (0xFF)); |
SHOW CREATE TABLE t1; |
SELECT PARTITION_DESCRIPTION FROM INFORMATION_SCHEMA.PARTITIONS WHERE TABLE_NAME='t1'; |
It returns the following output:
+-------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
| Table | Create Table |
|
+-------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
| t1 | CREATE TABLE `t1` (
|
`a` varbinary(10) DEFAULT NULL
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8
|
PARTITION BY LIST COLUMNS(`a`)
|
(PARTITION `p0` VALUES IN ('�') ENGINE = InnoDB) |
|
+-------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
+-----------------------+
|
| PARTITION_DESCRIPTION |
|
+-----------------------+
|
| '?' |
|
+-----------------------+
|
Notice:
- the SHOW CREATE output prints the byte 0xFF as is
- the INFORMATION_SCHEMA.PARTITIONS query changes it to the question mark
The expected behaviour would be to print 0xFF as _binary 0xff.
Attachments
Issue Links
- relates to
-
MDEV-20831 Table partitioned by LIST/RANGE COLUMNS(inet6) can be created, but not inserted into
- Closed
-
MDEV-20855 Crash with PARTITION BY LIST and extended characters
- Closed