Bug #92078 | Connector/ODBC bug when retrieving TEXT records using parameterized queries | ||
---|---|---|---|
Submitted: | 20 Aug 2018 9:53 | Modified: | 2 Apr 2019 22:44 |
Reporter: | RJW van den Hout | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 5.3.11 and 8.0.x | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[20 Aug 2018 9:53]
RJW van den Hout
[20 Aug 2018 10:14]
RJW van den Hout
FYI: this error does not occur when using non-parameterized queries or with 'NO_SSPS=1' set in connection string
[14 Oct 2018 0:27]
MySQL Verification Team
Thank you for the bug report and test case.
[16 Oct 2018 18:20]
K Scrupps
We are experiencing same issue with ODBC 8.0.12: presence of a mediumtext field in a select query causes no results to be returned when using a parameter in the query. Setting NO_SSPS=1 (client-side preparation) or using a parameter-less query returns results.
[28 Feb 2019 10:44]
Bogdan Degtyariov
Posted by developer: The bug is fixed in the version 8.0.16, but the fix is improved in 8.0.17.
[2 Apr 2019 22:44]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Connector/ODBC 5.3.13 / 8.0.16 releases, and here's the changelog entry that also stems from several other bug reports: An exception was emitted when fetching contents of a BLOB/TEXT records after executing a statement as a server-side prepared statement with a bound parameter. The workaround is not using parameters or specifying NO_SSPS=1 in the connection string; this allows the driver to fetch the data. Thank you for the bug report.