Bug #115048 Inserting with a paramset (SQL_ATTR_PARAMSET_SIZE) fails
Submitted: 17 May 2024 7:18 Modified: 17 Jun 5:47
Reporter: Yves Colombani Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:8.4.0 OS:CentOS (9)
Assigned to: CPU Architecture:x86

[17 May 2024 7:18] Yves Colombani
Description:
Inserting with a paramset (SQL_ATTR_PARAMSET_SIZE) fails with the following error:

[MySQL][ODBC 8.4(a) Driver][mysqld-5.7.41]No data supplied for parameters in prepared statement, SQLSTATE=HY000

The same code with the same driver manager and MySQL server works with previous releases of the connector.

How to repeat:
Execute an INSERT with a paramset
[25 Jun 2024 16:14] LaChelle Kazda
I am experiencing similar bug in another format. I have Excel reports that connect with MySQL with new ODBC 8.4 connector. In the Excel report I use cell parameters via Microsoft Query. I get same error message when I change the cell parameters and refresh the report/background query. The 5.7 version on other coworkers' laptops still works fine. It is the 8.4 version that is not allowing parameters to function, rendering several of my custom reports useless to non-MySQL users.

It would be helpful in the meantime if I were able to re-download the ODBC 5.7 version, but it is no longer available to download.
[25 Jun 2024 16:25] LaChelle Kazda
evidence of error message from comment on 2024-06-25

Attachment: 2024-06-25 comment evidence.png (image/png, text), 287.65 KiB.

[26 Jun 2024 9:34] Julian Howes
We also have this issue with the same error messages, in a range of software (SAS, Access, Excel, direct DB queries).
[15 May 13:02] MySQL Verification Team
Hello Yves Colombani,

Thank you for the bug report.
Could you please try with Connector/ODBC 9.X versions?

Regards,
Ashwini Patil
[22 May 16:13] LaChelle Kazda
Update: Upon our migration to MySQL 8.0 late last year, all bugs resolved.
[16 Jun 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[16 Jun 10:57] Yves Colombani
Just tried with odbc connector 9.3.0: it seems to be working now.