MySQL Bugs: #5681: Fetching time fields as SQL_C_TIME or SQL_C_TYPE

Bug #5681	Fetching time fields as SQL_C_TIME or SQL_C_TYPE_TIME is broken
Submitted:	21 Sep 2004 11:39	Modified:	9 Jun 2005 18:15
Reporter:	Yury Sidorov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	3.51.09	OS:	Windows (Windows 2000)
Assigned to:	Bugs System	CPU Architecture:	Any

Description:
Fetching time fields as SQL_C_TIME or SQL_C_TYPE_TIME is broken in 3.51.09 release. The driver returns 00:00:00 or NULLS. 

3.51.06 driver works fine.

How to repeat:
Bind time column as SQL_C_TIME or SQL_C_TYPE_TIME and fetch data.

Forgot to specify bug's severity and priority.

I submitted:  http://lists.mysql.com/myodbc/9515 -- to the myodbc mailing list before learning of this bug-tracking database.

I ran into the same issue, though on linux 2.2.20. The above link has a code change that I made to the 3.51.09 driver that seems to be taking care of the problem for me.

Same problem here with 3.51.10. I use ColdFusion and MySQL. When I use the 3.51.06 its working fine when I read a time-column. all newer drivers returns "00:00:00" or empty string.

When will this bug be fixed? Anybody know?

Same problem here. With MySQL 4.1's new authentication scheme, using MyODBC 3.51.06 is not an option. Neither is building from source. Have spent many hours trying to establish the cause of this problem, now there is no fix and the bug has been open since September. Please provide an estimated resolution time or a workaround I can implement in .NET. Thanks.

not only for windows. I attached test case. 

one must create table before using this test case:

create table aa (t time);
insert into aa values (now());

testcase. if it returs 0 : 0, bug is present.

Attachment: odbc.c (text/x-csrc), 4.01 KiB.

I have come across this problem with MyODBC version 3.51.11

Is there any progress / workaround available? (Other than setting up a new table and doing a Data Conversion)

Can I please have an update on this bug, as it is preventing me from moving forward from version 4.0 of MySQL
Thanks,
Neal

neal.hudson@o2.ie

Same problem here -- Windows 2003 Server Standart Ed. MySQL 4.1.10 MyODBC 3.51.11.
Please, somebody fix it, because we can't move on with our huge project, which uses MySQL; and we would have to put a bunch of limitations into user's manuals. Or downgrade their MySQLs or ask them to install older (4.0) next to their working 4.1s.. Along with MyODBCs..
Very many upset faces..

I found a reason and sent patch for review.

Same problem.  MySQL 4.1.7, ODBC versions 3.51.07 and up.  Time fields read as '00:00:00'.  How will we be advised when this patch becomes available?

It is real urgent!

Willem van Schalkwyk

Really really really URGENT! ASAP...
Anyone could release a patch/fix/update the sooner the better? Please?

The bug was found. Patch was sent for approval.

Thanks Vasily,

Do you know how long it takes for Approval?

Also, after the patch is Approved, does it get added to the current release version / previous versions, or put into the next release?

Thanks again

I fixed bug and attached new myodbc.dll. 

Yury:Can you test this dll file on your computer ? I want to be sure that I fixed it right. If all is ok I'll  insert this changes in distributive.

Thanks !

Thank you for your work on that issue.
That is really important for many partners and Customers.
Is there a way to get this fix available into the next ODBC connector, 3.51.12? Do you know the plan?
Regards,
Bertrand

Do we have any update on this issue?

Also, do you know when would the fix be included in the next Windows version of MyODBC?

Could you please mail the dll to me instead of the c-file, so I wouldn't have to compile it  ?

Thanx!

ttb@bluefish.dk

I'll look into this bug in a short time. The fix will be available as soon as possible.

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".

Vasily Kishkin fixed this bug and I tested a fixed version of driver. But Vasily did not post current status here.

Fetching time fields as SQL_C_TIME or SQL_C_TYPE_TIME is broken in 3.51.09, 3.51.10. 3.51.11 and MySQL 4.1.x
release. The driver returns 00:00:00 or NULLS. 

MySQL 4.0.24 and 3.51.06 driver works fine.

Could you force the release of myodbc 3.51.12? Or at least make a quick-beta?.. This delay is killing all our sales process and users moods..

3.51.12 with this bugfix is in testing and will be shipped soon.

If you'd be willing to test before release, please download and install from here:

ftp://ftp.mysql.com/pub/mysql/hidden/connectors/odbc/3.51.12/MyODBC-3.51.12-win32.exe

And report success/failure back to this bug report.

Had this problem with v3.51.11.  Just tried installing 3.51.12 and it is fixed.  (I'm using ADO2.5 in VB6)

I use Ado 2.8 and VB6, with Connector/ODBC 3.51.12 it is fixed.

Fix works for me too.

H'Ray,  Ant

With the following constellation I still get the wrong time:
MySQL 4.0.18
MyODBC 3.51.12
Office Access 2003 SP1

Kind regards, Peter