MySQL Bugs: #25846: MyODBC does not recognize TIME (hh:mm:ss) and DATE (yy:mm:dd)

Bug #25846	MyODBC does not recognize TIME (hh:mm:ss) and DATE (yy:mm:dd)
Submitted:	25 Jan 2007 14:52	Modified:	9 Mar 2007 12:25
Reporter:	Bogdan Degtyariov
Status:	Closed
Category:	Connector/ODBC	Severity:	S2 (Serious)
Version:	3.51.12	OS:	Any (All OS)
Assigned to:	Bogdan Degtyariov	Target Version:
Tags:	date, time, SQLBindCol, SQLFetch

Description:
When return the result into the bound buffer MyODBC performs incorrect data
transformation TIME->DATE. Actually it uses the string length as the indicator of the
type and recognizes TIME (hh:mm:ss) as DATE (yy:mm:dd). Which may display unpredictable
results.

How to repeat:
It can be recreated in Crystal Reports. Just try to retrieve a TIME field.
Will upload C test case later.

Suggested fix:
Make difference between ":" and "-" and treat them as TIME and DATE indicators
accordingly.

Bugs #24867 and #25432 are duplicated by this bug

This bug has been fixed in MyODBC 3.51.14 (Next GA version of MyODBC)

An entry ahs been added to the 3.51.14 changelog.

the bug persist

i still getting back date/time values on time fields

Bogdan,

Could you please verify if this bug still exist or comment the exactly
version the fix will be present. See: http://bugs.mysql.com/bug.php?id=29255.
Thanks in advance.

Checked the bug with MyODBC 3.51.22. Works as expected.
The problem with Excel is that the bounding buffer for DATE and TIME columns is
TIMESTAMP. If fill the buffer from the TIME column the TIMESTAMP variable will contain
the following information "0000-00-00 HH:MM:SS". As ero dates are not allowed the date
component is set to the current date. See the [c] section which corresponds to the case
when time column is bound to TIMESTAMP buffer:

http://msdn2.microsoft.com/en-us/library/ms712436(VS.85).aspx

DATE result bound to TIMESTAMP result is ok. Time component can be 00:00:00 accordingly
to MSDN specification:

http://msdn2.microsoft.com/en-us/library/ms712474(VS.85).aspx