[KLUG Members] MySQL and Date Fields

[Jamie McCarthy]

mlueck at lueckdatasystems.com (Michael Lueck) writes:

> OK, I looked up the old posting. The grumble of Windows apps via
> the ODBC driver to MySQL was as follows:
> 
> >>
> If I post the times 01:00:00 or 00:45:00 it either refuses to
> post them or posts the latter as 45:00:00!
> <<
> 
> Which the answer was...
> 
> >>
> Using MyODBC 2.5, tables copied fine, and all of the data types
> did as well.  Using ODBC 3.5, date/time columns translated as
> VARCHAR.  I wouldn't be surprised if there were other gotchas.
> <<

I'm gonna guess that's one of these bugs:
http://bugs.mysql.com/bug.php?id=8384
http://bugs.mysql.com/bug.php?id=10080

Looks like a problem with ODBC Connector 3.51.11.  There are a couple
of bugs ranked Serious and Critical in MySQL's bug-tracker and
they've gone unfixed for several months now.  That's not typical in
my experience.  Obviously if you need to connect from Windows this
is a very serious problem.

I can't tell from the writeups if MyODBC earlier than 3.51.11 also
exhibits this problem.  The first bug writeup implies (but doesn't
state outright) that the problem was not present with 3.51.10.

While I don't see where to download 3.5.x, 6 < x < 11, I'm sure
copies wouldn't be that hard to find.  The 3.51.06 windows source,
first 'stable' release in the 3.51.x series, from February 2003, is
downloadable:
<http://dev.mysql.com/downloads/connector/odbc/3.51.html#Source>

Changelog:
<http://dev.mysql.com/get/Downloads/MyODBC3/ChangeLog/from/pick>

I don't use ODBC so I'm a little out of my league here, but yes,
it does look like at least the current version of that connector
has serious bugs.  :(
-- 
  Jamie McCarthy
 http://mccarthy.vg/
  jamie at mccarthy.vg