Bug #80320 | MySQL Unicode Driver Fails when 1st character of query a Tab or C/R | ||
---|---|---|---|
Submitted: | 9 Feb 2016 15:15 | Modified: | 9 Feb 2023 8:12 |
Reporter: | Joseph Leathlean | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 5.03.04 | OS: | Windows (64 bit Server) |
Assigned to: | CPU Architecture: | Any |
[9 Feb 2016 15:15]
Joseph Leathlean
[10 Feb 2016 11:50]
Chiranjeevi Battula
Hello Joseph Leathlean, Thank you for the bug report. Verified this behavior on MySQL Connector/ODBC 5.3.4 Unicode Driver. Thanks, Chiranjeevi.
[10 Feb 2016 11:51]
Chiranjeevi Battula
Unicode screenshot.
Attachment: 80320_Unicode.PNG (image/png, text), 168.15 KiB.
[10 Feb 2016 11:52]
Chiranjeevi Battula
ANSI screenshot.
Attachment: 80320_ANSI.PNG (image/png, text), 168.83 KiB.
[27 Aug 2019 7:14]
Thejaka Maldeniya
This issue is still not fixed in mysql-connector-odbc-8.0.17-winx64. Took me a long time to figure out what was causing the error. It was a leading C/R that was used to format the code.
[9 Feb 2023 8:12]
Bogdan Degtyariov
Posted by developer: This issue is no longer repeatable with Connector/ODBC 8.0 Unicode Driver. Closing the bug with "Could not reproduce" status.
[9 Feb 2023 8:18]
Bogdan Degtyariov
Posted by developer: Tested using ODBC driver version 8.0.32. The query with tab and <CR> run without problems: select * from OPENQUERY(MYSQL, ' SELECT * FROM test.data_test')