Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL)
-
None
-
10.2.12
Description
create table t1 (a int);
|
insert into t1 values (1),(3),(2);
|
Compare
explain format=json select * from t1 order by a;
|
EXPLAIN
|
{
|
"query_block": {
|
"select_id": 1,
|
"read_sorted_file": {
|
"filesort": {
|
"sort_key": "t1.a",
|
"table": {
|
"table_name": "t1",
|
"access_type": "ALL",
|
"rows": 3,
|
"filtered": 100
|
}
|
}
|
}
|
}
|
}
|
with
explain format=json select * from t1 order by a desc;
|
EXPLAIN
|
{
|
"query_block": {
|
"select_id": 1,
|
"read_sorted_file": {
|
"filesort": {
|
"sort_key": "t1.a",
|
"table": {
|
"table_name": "t1",
|
"access_type": "ALL",
|
"rows": 3,
|
"filtered": 100
|
}
|
}
|
}
|
}
|
}
|
It would be nice to print ASC or DESC somehow. Maybe, only print DESC, because ASC is default so for the sake of brevity it should be omitted.
psergey What should we do when we have multiple sort keys and multiple orders associated with them
An example would be
create table t1 ( a int , b int);
insert into t1 values (1,2) , (3,4) , (2,3);
select * from t1 order by a asc, b desc;
Should we attach the ASC/DESC associated with the first key in the sort order?
Attaching ASC/DESC for all sort keys does not make sense to me