Bug #96280 | prepared cursor failed to fetch/decode result of varbinary columns | ||
---|---|---|---|
Submitted: | 23 Jul 2019 4:27 | Modified: | 21 Oct 2022 21:14 |
Reporter: | zy t | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / Python | Severity: | S3 (Non-critical) |
Version: | since 8.0.11, 8.0.17 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[23 Jul 2019 4:27]
zy t
[24 Jul 2019 12:15]
MySQL Verification Team
Hello zy t! Thank you for the report. regards, Umesh
[12 Nov 2019 20:01]
OCA Admin
Contribution submitted via Github - Fix BUG96280 (*) Contribution by Naoki Someya (Github n-someya, mysql-connector-python/pull/55#issuecomment-552143467): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: git_patch_338568511.txt (text/plain), 4.36 KiB.
[21 Oct 2022 21:14]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Connector/Python 8.0.32 release, and here's the proposed changelog entry from the documentation team: When fetching results from a prepared cursor using the pure Python implementation, it would fail if the VARBINARY column contained bytes that could not be decoded. The bytes are now returned if they cannot be decoded. Thanks to Naoki Someya for the contribution. Thank you for the bug report.