Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL)
-
None
Description
This script being run in a Linux utf8 console:
SET NAMES utf8; |
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (a SET('a,bü')); |
returns this error message:
ERROR 1367 (22007): Illegal set 'a,ü' value found during parsing
|
The error message looks wrong. It should be this instead:
ERROR 1367 (22007): Illegal set 'a,ü' value found during parsing
|
Attachments
Issue Links
- duplicates
-
MDEV-11146 SP variables of the SET data type erroneously allow values with comma
-
- Closed
-
- relates to
-
MDEV-11146 SP variables of the SET data type erroneously allow values with comma
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Affects Version/s | 10.1 [ 16100 ] | |
Affects Version/s | 10.3 [ 22126 ] |
Component/s | Character Sets [ 10801 ] | |
Component/s | OTHER [ 10125 ] |
Link |
This issue duplicates |
Fix Version/s | N/A [ 14700 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 78101 ] | MariaDB v4 [ 151134 ] |
The patch for "
MDEV-11146SP variables of the SET data type erroneously allow values with comma" fixed this problem.