[MDEV-11155] Bad error message when creating a SET column with comma and non-ASCII characters Created: 2016-10-27  Updated: 2017-11-15  Resolved: 2017-11-15

Status: Closed
Project: MariaDB Server
Component/s: Character Sets
Affects Version/s: 5.5, 10.0, 10.1, 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Alexander Barkov Assignee: Alexander Barkov
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-11146 SP variables of the SET data type err... Closed
Relates
relates to MDEV-11146 SP variables of the SET data type err... Closed

 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



 Comments   
Comment by Alexander Barkov [ 2017-11-15 ]

The patch for "MDEV-11146 SP variables of the SET data type erroneously allow values with comma" fixed this problem.

Generated at Thu Feb 08 07:47:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.