topic Re: ERROR with MySQL: The value '32805' could not be converted to type integer(2-bytes) in App Development

ERROR with MySQL: The value '32805' could not be converted to type integer(2-bytes)

Kellerassel — Fri, 15 Nov 2024 23:25:41 GMT

I want to execute a Query in MySQL filtering by date.

SQL SELECT * FROM `my_database`.`my_table` WHERE date >= '2021-12-08'

But I get this error:

ERROR: The value '32805' could not be converted to type integer(2-bytes)

This query works if I run it directly in our MySQL-Database, it works if I run it on QlikView and it works on any other table executed from Qlik Sense. But it doesn't work on this specific table executing from Qlik Sense.

What can be the reason for this?

Info: Field "date" is of type "date".

Re: ERROR with MySQL: The value '32805' could not be converted to type integer(2-bytes)

marcus_sommer — Wed, 15 Dec 2021 14:12:25 GMT

Did you try it without the where-clause? The occurring error may not have a relation to the date-field else any other field may have a conflict between the stored data and their data-type and how the driver tries to handle it.

- Marcus

Re: ERROR with MySQL: The value '32805' could not be converted to type integer(2-bytes)

Kellerassel — Thu, 16 Dec 2021 09:17:42 GMT

It works without the 'Where'-clause.

Turned out, that the error occurs only when I included a specific column (let's call it "ID", type smallint(5) ) in the selection AND filtered by date. If I filtered by date but excluded ID it worked, if I included ID but didn't filter by date it worked also. But together, then I get the above error.

The solution was to multiply ID by 1 inside the SELECT statement. Then it suddenly worked.

It's not really a solution, more a workaround.

Maybe you know what's up with that.

Re: ERROR with MySQL: The value '32805' could not be converted to type integer(2-bytes)

marcus_sommer — Thu, 16 Dec 2021 09:59:12 GMT

I think your multiplying means a conversion into another data-type so that the driver doesn't handle it anymore as smallint. Your used driver may not recognize this data-type and/or interpreting it differently in any way. Therefore you may look if this driver could be configured in any way or maybe there are alternativ drivers available.

- Marcus