Bug #27474 | myODBC 3.51 and VISTA | ||
---|---|---|---|
Submitted: | 27 Mar 2007 14:32 | Modified: | 28 May 2013 8:21 |
Reporter: | Zero-G. _ | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S1 (Critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any |
[27 Mar 2007 14:32]
Zero-G. _
[28 Mar 2007 4:42]
Valeriy Kravchuk
Thank you for a problem report. What exact version of MyODBC, 3.5.1.xx, do you use? Send als SHOW CREATE TABLE results for that table you are selecting from.
[28 Apr 2007 23: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".
[31 May 2007 13:34]
haroon chaudhry
I have same problem here are releavent info MySQL server 5.0.27 ODBC Connector version 3.51.15 ODBC can't properly read columns selected as select date_format(someDateColumn,'%M %e, %Y'); If I replace select statement with select someDateColumn; It works fine, same query works using driver 3.51.12 (I think earlier version were also working) I tried to "manually" formate date using select concat('',monthname(datec),' ', day(datec),', ',year(datec)) ; but it still does not work. Any idea how to fix it? or any work around? Thanks Haroon
[31 May 2007 13:36]
haroon chaudhry
Some more details, Server is running on Fedora Core 5 and I tried various clients including WinXP, Windows Server 2003, Win98 All have same problem Thanks Haroon
[28 May 2013 8:21]
Bogdan Degtyariov
This bug has been fixed by introducing the option "Always handle binary function result as character data" or by using NO_BINARY_RESULT=1 in the connection string. Bug is closed.