Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
13.1
-
Can result in unexpected behaviour
Description
testcase:
--source include/have_sequence.inc
|
create table t1 (a varchar(10), key(a)); |
insert into t1 select concat('x', seq) from seq_1_to_100; |
insert into t1 values ('a"1'), ('a"2'), ('a"3'); |
set optimizer_trace='enabled=on'; |
--sorted_result
|
select a from t1 where a in ('a"1', 'a"2', 'a"3'); |
select json_detailed(json_extract(trace, '$**.range_scan_alternatives[*].ranges')) |
as ranges |
from information_schema.optimizer_trace; |
drop table t1; |
gives
select json_detailed(json_extract(trace, '$**.range_scan_alternatives[*].ranges'))
|
as ranges
|
from information_schema.optimizer_trace;
|
ranges
|
[
|
[
|
"(a\\\"1) <= (a) <= (a\\\"1)",
|
"(a\"2) <= (a) <= (a\"2)",
|
"(a\"3) <= (a) <= (a\"3)"
|
]
|
]
|
Attachments
Issue Links
- is caused by
-
MDEV-39720 Optimizer Trace doesn't quote string values, may have invalid JSON
-
- Closed
-