Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
possible_keys=NULL in MariaDB, while it is 'd' in MySQL.
MySQL's output looks more logical. Need to investigate where the difference comes from.
rocksdb.type_float_indexes [ fail ]
|
Test ended at 2016-12-02 12:30:35
|
 |
CURRENT_TEST: rocksdb.type_float_indexes
|
--- /home/psergey/dev-git/10.2-mariarocks/storage/rocksdb/mysql-test/rocksdb/r/type_float_indexes.result 2016-10-06 17:30:25.595958776 +0000
|
+++ /home/psergey/dev-git/10.2-mariarocks/storage/rocksdb/mysql-test/rocksdb/r/type_float_indexes.reject 2016-12-02 12:30:35.681517143 +0000
|
@@ -85,7 +85,7 @@
|
(4644,1422.22,466664.999,0.5,5);
|
EXPLAIN SELECT DISTINCT d FROM t1 ORDER BY d;
|
id select_type table type possible_keys key key_len ref rows Extra
|
-1 SIMPLE t1 index d d 9 NULL # Using index
|
+1 SIMPLE t1 index NULL d 9 NULL # Using index
|
SELECT DISTINCT d FROM t1 ORDER BY d;
|
d
|
-1
|
@@ -114,7 +114,7 @@
|
(4644,1422.22,466664.999,0.5,5);
|
EXPLAIN SELECT DISTINCT d FROM t1 ORDER BY d;
|
id select_type table type possible_keys key key_len ref rows Extra
|
-1 SIMPLE t1 index d d 9 NULL # Using index
|
+1 SIMPLE t1 index NULL d 9 NULL # Using index
|
SELECT DISTINCT d FROM t1 ORDER BY d;
|
d
|
-1
|
@@ -146,7 +146,7 @@
|
ERROR 23000: Duplicate entry '1.2345' for key 'f'
|
EXPLAIN SELECT DISTINCT f FROM t1 ORDER BY f;
|
id select_type table type possible_keys key key_len ref rows Extra
|
-1 SIMPLE t1 index f f 5 NULL # Using index
|
+1 SIMPLE t1 index NULL f 5 NULL # Using index
|
SELECT DISTINCT f FROM t1 ORDER BY f;
|
f
|
-1
|
@@ -177,7 +177,7 @@
|
(1.2345,0,0,0,6);
|
EXPLAIN SELECT DISTINCT f FROM t1 ORDER BY f;
|
id select_type table type possible_keys key key_len ref rows Extra
|
-1 SIMPLE t1 index f f 5 NULL # Using index
|
+1 SIMPLE t1 index NULL f 5 NULL # Using index
|
SELECT DISTINCT f FROM t1 ORDER BY f;
|
f
|
-1
|
Attachments
Issue Links
- is part of
-
MDEV-9658 Make MyRocks in MariaDB stable
- Closed