[MDEV-8253] EXPLAIN SELECT prints unexpected characters - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.0(EOL), 10.1(EOL)
Fix Version/s: 10.1.8
Component/s: Character Sets, Optimizer
Labels:
- upstream-not-affected

Sprint:
10.1.8-2, 10.1.8-3

Description

In this script:

DROP TABLE IF EXISTS t1;

CREATE TABLE t1 (a DECIMAL(10,1),b DECIMAL(10,1),c VARCHAR(10),d VARCHAR(10));

INSERT INTO t1 VALUES (1.5,1.5,'1','1'),(3.5,3.5,'3','3');

explain EXTENDED SELECT * FROM t1 WHERE

  COALESCE(c,0)='3 ' AND

  COALESCE(d,0)=COALESCE(c,0);

SHOW WARNINGS;

the condition gets rewritten by optimizer by replacing COALESCE(c,0) to '3'.
It seems something goes wrong with the created replacement Item corresponding to '3', so the warnings generated by the EXPLAIN query return dirty characters:

+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| Level | Code | Message                                                                                                                                                                                                     |

+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| Note  | 1003 | select `test`.`t1`.`a` AS `a`,`test`.`t1`.`b` AS `b`,`test`.`t1`.`c` AS `c`,`test`.`t1`.`d` AS `d` from `test`.`t1` where ((coalesce(`test`.`t1`.`c`,0) = '3 ') and (coalesce(`test`.`t1`.`d`,0) = '¥¥'))   |

+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Notice the unexpected YEN signs in the above output.

Attachments

Activity

Ascending order - Click to sort in descending order

Alexander Barkov created issue - 2015-06-01 10:01

Alexander Barkov made changes - 2015-06-01 10:02

Field	Original Value	New Value
Description	In this script: {code} DROP TABLE IF EXISTS t1; CREATE TABLE t1 (a DECIMAL(10,1),b DECIMAL(10,1),c VARCHAR(10),d VARCHAR(10)); INSERT INTO t1 VALUES (1.5,1.5,'1','1'),(3.5,3.5,'3','3'); explain EXTENDED SELECT * FROM t1 WHERE COALESCE(c,0)='3 ' AND COALESCE(d,0)=COALESCE(c,0); SHOW WARNINGS; {code} the condition gets rewritten by optimizer by replacing COALESCE(c,0) to '3'. It seems something goes wrong with the created replacement Item corresponding to '3', so the warnings generated by the EXPLAIN query return dirty characters: {format} +-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ \| Level \| Code \| Message \| +-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ \| Note \| 1003 \| select `test`.`t1`.`a` AS `a`,`test`.`t1`.`b` AS `b`,`test`.`t1`.`c` AS `c`,`test`.`t1`.`d` AS `d` from `test`.`t1` where ((coalesce(`test`.`t1`.`c`,0) = '3 ') and (coalesce(`test`.`t1`.`d`,0) = '¥¥')) \| +-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ {format}	In this script: {code} DROP TABLE IF EXISTS t1; CREATE TABLE t1 (a DECIMAL(10,1),b DECIMAL(10,1),c VARCHAR(10),d VARCHAR(10)); INSERT INTO t1 VALUES (1.5,1.5,'1','1'),(3.5,3.5,'3','3'); explain EXTENDED SELECT * FROM t1 WHERE COALESCE(c,0)='3 ' AND COALESCE(d,0)=COALESCE(c,0); SHOW WARNINGS; {code} the condition gets rewritten by optimizer by replacing COALESCE(c,0) to '3'. It seems something goes wrong with the created replacement Item corresponding to '3', so the warnings generated by the EXPLAIN query return dirty characters: {format} +-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ \| Level \| Code \| Message \| +-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ \| Note \| 1003 \| select `test`.`t1`.`a` AS `a`,`test`.`t1`.`b` AS `b`,`test`.`t1`.`c` AS `c`,`test`.`t1`.`d` AS `d` from `test`.`t1` where ((coalesce(`test`.`t1`.`c`,0) = '3 ') and (coalesce(`test`.`t1`.`d`,0) = '¥¥')) \| +-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ {format}

Alexander Barkov made changes - 2015-06-01 10:02

Description

In this script:
{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a DECIMAL(10,1),b DECIMAL(10,1),c VARCHAR(10),d VARCHAR(10));
INSERT INTO t1 VALUES (1.5,1.5,'1','1'),(3.5,3.5,'3','3');
explain EXTENDED SELECT * FROM t1 WHERE
COALESCE(c,0)='3 ' AND
COALESCE(d,0)=COALESCE(c,0);
SHOW WARNINGS;
{code}
the condition gets rewritten by optimizer by replacing COALESCE(c,0) to '3'.
It seems something goes wrong with the created replacement Item corresponding to '3', so the warnings generated by the EXPLAIN query return dirty characters:

{format}
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Level | Code | Message |
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Note | 1003 | select `test`.`t1`.`a` AS `a`,`test`.`t1`.`b` AS `b`,`test`.`t1`.`c` AS `c`,`test`.`t1`.`d` AS `d` from `test`.`t1` where ((coalesce(`test`.`t1`.`c`,0) = '3 ') and (coalesce(`test`.`t1`.`d`,0) = '¥¥')) |
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
{format}

In this script:
{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a DECIMAL(10,1),b DECIMAL(10,1),c VARCHAR(10),d VARCHAR(10));
INSERT INTO t1 VALUES (1.5,1.5,'1','1'),(3.5,3.5,'3','3');
explain EXTENDED SELECT * FROM t1 WHERE
COALESCE(c,0)='3 ' AND
COALESCE(d,0)=COALESCE(c,0);
SHOW WARNINGS;
{code}
the condition gets rewritten by optimizer by replacing COALESCE(c,0) to '3'.
It seems something goes wrong with the created replacement Item corresponding to '3', so the warnings generated by the EXPLAIN query return dirty characters:

{noformat}
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Level | Code | Message |
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Note | 1003 | select `test`.`t1`.`a` AS `a`,`test`.`t1`.`b` AS `b`,`test`.`t1`.`c` AS `c`,`test`.`t1`.`d` AS `d` from `test`.`t1` where ((coalesce(`test`.`t1`.`c`,0) = '3 ') and (coalesce(`test`.`t1`.`d`,0) = '¥¥')) |
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
{noformat}

Alexander Barkov made changes - 2015-06-01 10:03

Description

In this script:
{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a DECIMAL(10,1),b DECIMAL(10,1),c VARCHAR(10),d VARCHAR(10));
INSERT INTO t1 VALUES (1.5,1.5,'1','1'),(3.5,3.5,'3','3');
explain EXTENDED SELECT * FROM t1 WHERE
COALESCE(c,0)='3 ' AND
COALESCE(d,0)=COALESCE(c,0);
SHOW WARNINGS;
{code}
the condition gets rewritten by optimizer by replacing COALESCE(c,0) to '3'.
It seems something goes wrong with the created replacement Item corresponding to '3', so the warnings generated by the EXPLAIN query return dirty characters:

{noformat}
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Level | Code | Message |
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Note | 1003 | select `test`.`t1`.`a` AS `a`,`test`.`t1`.`b` AS `b`,`test`.`t1`.`c` AS `c`,`test`.`t1`.`d` AS `d` from `test`.`t1` where ((coalesce(`test`.`t1`.`c`,0) = '3 ') and (coalesce(`test`.`t1`.`d`,0) = '¥¥')) |
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
{noformat}

In this script:
{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a DECIMAL(10,1),b DECIMAL(10,1),c VARCHAR(10),d VARCHAR(10));
INSERT INTO t1 VALUES (1.5,1.5,'1','1'),(3.5,3.5,'3','3');
explain EXTENDED SELECT * FROM t1 WHERE
COALESCE(c,0)='3 ' AND
COALESCE(d,0)=COALESCE(c,0);
SHOW WARNINGS;
{code}
the condition gets rewritten by optimizer by replacing COALESCE(c,0) to '3'.
It seems something goes wrong with the created replacement Item corresponding to '3', so the warnings generated by the EXPLAIN query return dirty characters:

{noformat}
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Level | Code | Message |
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Note | 1003 | select `test`.`t1`.`a` AS `a`,`test`.`t1`.`b` AS `b`,`test`.`t1`.`c` AS `c`,`test`.`t1`.`d` AS `d` from `test`.`t1` where ((coalesce(`test`.`t1`.`c`,0) = '3 ') and (coalesce(`test`.`t1`.`d`,0) = '¥¥')) |
+-------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
{noformat}
Notice the unexpected YEN signs in the above output.

Alexander Barkov made changes - 2015-09-23 06:32

Rank

Ranked higher

Alexander Barkov made changes - 2015-09-23 06:34

Rank

Ranked higher

Alexander Barkov made changes - 2015-09-23 06:35

Sprint

10.1.8-2 [ 14 ]

Alexander Barkov made changes - 2015-09-23 06:35

Rank

Ranked higher

Alexander Barkov made changes - 2015-09-23 12:12

Fix Version/s		10.1.8 [ 19605 ]
Fix Version/s	10.1 [ 16100 ]
Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Closed [ 6 ]

Alexander Barkov made changes - 2015-09-23 15:26

Sprint

10.1.8-2 [ 14 ]

10.1.8-2, 10.1.8-3 [ 14, 15 ]

Alexander Barkov made changes - 2015-09-23 19:39

Labels

upstream-not-affected

Alexander Barkov added a comment - 2015-09-23 19:39

MySQL-5.7.8-rc-debug is not affected

Alexander Barkov added a comment - 2015-09-23 19:39 MySQL-5.7.8-rc-debug is not affected

Sergei Golubchik made changes - 2021-12-06 21:41

Workflow

MariaDB v3 [ 69808 ]

MariaDB v4 [ 149229 ]

People

Assignee:: Alexander Barkov

Reporter:: Alexander Barkov

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2015-06-01 10:01

Updated:: 2015-09-23 19:39

Resolved:: 2015-09-23 12:12

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Activity

People

Dates

Git Integration