[MCOL-4290] Join query errors when using upper case table names Created: 2020-09-03  Updated: 2021-09-16  Resolved: 2020-09-21

Status: Closed
Project: MariaDB ColumnStore
Component/s: MDB Plugin
Affects Version/s: 1.5.3
Fix Version/s: 5.4.1

Type: Bug Priority: Critical
Reporter: suresh ramagiri Assignee: David Hall (Inactive)
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MCOL-4144 Error when using upper case database ... Closed

 Description   

It is reported by a customer, that cross engine join query having an upper cased INNODB table, throwing ERROR.

Here are the repro steps:

MariaDB [inno]> CREATE TABLE INNO (a int, b varchar(10));
Query OK, 0 rows affected (0.004 sec)

MariaDB [inno]> create table cs (a int, b varchar(10)) engine=columnstore;
Query OK, 0 rows affected (1.120 sec)

MariaDB [inno]> select * from cs a, INNO b where a.a=b.a;
ERROR 1815 (HY000): Internal error: fatal error runing mysql_real_query() in libmysql_client lib (1146) (Table 'inno.inno' doesn't exist)

MariaDB [inno]> select @@lower_case_table_names;
--------------------------

@@lower_case_table_names

--------------------------

0

--------------------------
1 row in set (0.000 sec)

MariaDB [inno]> select @@version;
----------------

@@version

----------------

10.5.5-MariaDB

----------------
1 row in set (0.001 sec)

 Comments   
Comment by suresh ramagiri [ 2020-09-03 ]

Workaround, is to set the lower_case_table_names to "1", which makes table names and database names are stored in lowercase and compared in a case-insensitive manner.

Comment by David Hall (Inactive) [ 2020-09-21 ]

This is a symptom of MCOL-4144, so we are closing this. See MCOL-4144 for status.

Generated at Thu Feb 08 02:49:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.