Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Do
-
1.1.5
-
Centos release 7.4
Description
A number of operators in where clause filtering do not work and return wrong results. For example:
MariaDB [information_schema]> select table_schema, table_name, object_id, column_count from columnstore_tables where table_name in ('t1','t2');
---------------------------------------------+
table_schema | table_name | object_id | column_count |
---------------------------------------------+
test | t1 | 24442 | 1 |
---------------------------------------------+
1 row in set (0.04 sec)
MariaDB [information_schema]> select table_schema, table_name, object_id, column_count from columnstore_tables where table_name in ('t2');
---------------------------------------------+
table_schema | table_name | object_id | column_count |
---------------------------------------------+
test | t2 | 24446 | 2 |
datos | t2 | 25221 | 2 |
---------------------------------------------+
2 rows in set (0.06 sec)
MariaDB [information_schema]> select table_schema, table_name, object_id, column_count from columnstore_tables where table_name like 't%';
Empty set (0.01 sec)
MariaDB [information_schema]> select table_schema, table_name, object_id, column_count from columnstore_tables where table_schema > 't';
Empty set (0.02 sec)
This worked:
MariaDB [information_schema]> select table_schema, table_name, object_id, column_count from columnstore_tables where table_name = 't1';
---------------------------------------------+
table_schema | table_name | object_id | column_count |
---------------------------------------------+
test | t1 | 24442 | 1 |
---------------------------------------------+
1 row in set (0.04 sec)
This prevents one from developing "admin" scripts" to do analysis on objects in the database.