Qlik MySQL connector data type conversion issue in Qlik Sense February 2022

Andreas_Giesbrecht — Thu, 31 Mar 2022 14:31:41 GMT

When using the Qlik MySQL connector (in version February 2022) you might encounter a reload error which seems to be related to a data type conversion with bit(1) data types where the following error message occurs:

"The value 'True' could not be converted to type integer(8-bytes)"

For other data types like INT, VARCHAR, etc. there seems to be no problem for the data reloads.

Environment

Qlik Sense February 2022
Qlik ODBC connector package February 2022

Resolution

This issue has been identified as a defect which resolution is still in progress.

Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID QB-9827 for reference.

Workaround:

In order to solve the problem you have the following options:

Use instead of the MySQL connector an ODBC System DSN connection via MySQL ODBC driver
Just downgrade the Qlik ODBC connector package version to version August 2021. Before any downgrade please first backup the original "QvOdbcConnectorPackage" folder and test the downgraded version on a development environment.

Cause

Product Defect ID: QB-9827

Re: Qlik MySQL connector data type conversion issue in Qlik Sense February 2022

chris-s — Tue, 12 Apr 2022 11:43:42 GMT

I had the same issue at a customer's site.

Another workaround is manually casting all bit(1) fields to unsigned integers using

cast(<Field>, UNSIGNED) AS <Field>,

for all fields.

Drawback is, that this way a star-select isn't possible anymore and if you use MySQL heavily you'll probably have to update a lot of scripts.