Bug #33808 | MyODBC 51/Access ODBC CONVERT() causes error | ||
---|---|---|---|
Submitted: | 10 Jan 2008 20:52 | Modified: | 14 Mar 2008 18:43 |
Reporter: | Erica Moss | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 5.1.1 | OS: | Windows (xp2 sp2) |
Assigned to: | Jim Winstead | CPU Architecture: | Any |
[10 Jan 2008 20:52]
Erica Moss
[10 Jan 2008 20:54]
Erica Moss
dump file for bug database
Attachment: northwind.dump (application/octet-stream, text), 330.18 KiB.
[11 Jan 2008 19:31]
Erica Moss
access database file
Attachment: bug.mdb (application/msaccess, text), 420.00 KiB.
[31 Jan 2008 23:26]
Jim Winstead
this is probably because we're reporting we support SQL_FN_CVT_CONVERT in SQL_CONVERT_FUNCTIONS, but MySQL's CONVERT() is not like that mandated by the ODBC spec. SQL_FN_CVT_CAST needs to be confirmed. it may also not be okay because of the limited types that MySQL allows in CAST().
[28 Feb 2008 21:01]
Jim Winstead
Don't report that CAST() and CONVERT() are supported
Attachment: bug33808.diff (text/plain), 946 bytes.
[12 Mar 2008 15:32]
Lawrenty Novitsky
approved
[12 Mar 2008 15:53]
Jim Winstead
The fix is committed, and will be included in the 5.1.3 release.
[14 Mar 2008 18:39]
MC Brown
A note has been added to the 5.1.3 changelog: Connector/ODBC erroneously reported that it supported the CAST() and CONVERT() ODBC functions for parsing values in SQL statements, which could lead to bad SQL generation during a query.