Unable to add tables into Data Manager (GUI) due to utf8mb4 ODBC mysql error

[AGEric]

We have been struggling with this error and have received not solution from Qlik support.
It's been months and Qlik tech support said to stop using the Data Manager entirely becuase they can't fix it.

We have many Qlik apps with dozens of Sheets created so a heavy investment in Qlik.
Th bug is basically we cannot use the Data Manager (DM) any more.
The MySQl database has been connected to Qlik for 4+ years.

The bug appears by using the DM to add tables from the Mysql connection.

Browsing a connection works correctly.

Browsing the tables list works fine.

Browsing the table rows works fine.

Clicking the 'Add' is where things go sideways. The DLE errors with :

ODBC Wrapper: Unable to execute SQLForeignKeys:
[Qlik][MySQL] Illegal mix of collations
(utf8mb3_tolower_ci,IMPLICIT) and (
utf8mb3_general_ci,IMPLICIT)
for operation '='

In throwing this error (again, successfully querying data in the DM 'preview') the DM does not load the table and the error halts the UI. Without the ability to alter the schema in Qlik means all our work is frozen.
We tried to edit an existing App and the DM broke and we lost ALL of our data model, all tables. so it's a landmine bug.

We checked every table and column and there is no utf8mb3* collation
We exported the entire database to .sql and used 'grep' to confirm utf8mb4 and NOT utf8mb3.
We used SQL to query the information_schema to also confirm that all tables/columns are utf8mb4_unicode_ci* and not utf8mb3.

We suspect the Qlik ODBC is doing something during the DMV loading event that it should not be doing, maybe looking at the mysql.information_schema?

As a test, we ran this:

CREATE TABLE no_charset (
my_column VARCHAR(255)
);

SHOW CREATE TABLE no_charset;

and it returned a create statement which confirms the database is correctly defaulting to utf8mb4*:

CREATE TABLE `no_charset` (
`my_row_id` bigint unsigned NOT NULL AUTO_INCREMENT,
`my_column` varchar(255) COLLATE utf8mb4_general_ci DEFAULT NULL,
PRIMARY KEY (`my_row_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci

Our conclusion is that Qlik has a serious ODBC Mysql bug that they are refusing to address.

If anyone has seen this Mysql + ODBC error please send a reply along.
Thank you

[David_Friend]

@AGEric hey Eric this topic is a bit outside of my typical scope but I'll try and at least help, do you have a case number?

[janyf]

Hello , is there any solution for this ?