MySQL Bugs: #49953: MyODBC 5 datetime data type changed into varchar(19) in powerbuilder

Bug #49953	MyODBC 5 datetime data type changed into varchar(19) in powerbuilder
Submitted:	28 Dec 2009 8:49	Modified:	29 May 2013 6:06
Reporter:	Sulaeman Bong	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	5.1	OS:	Any
Assigned to:	Lawrenty Novitsky	CPU Architecture:	Any

Description:
Before using MySQL ODBC/Connector 5.1, i'm using MySQL ODBC/Connector 3.51 which is fine using option=135168 in creating datawindow for datetime datatype, but after using the newest ODBC/Connector, the datatype for datetime changed into varchar(19), are there any ways to resolve this issue ? Thanks.

How to repeat:
Use MySQL ODBC/Connector in creating datawindow which has datetime datatype column in it, and it will change to varchar(19) instead of datetime.

Hi Sulaeman and thanks for your report.

Unfortunately, Sybase does not offer a proper solution for me to test their SW and all licenses I had are long expired... So we'll have to do it the hard way.

First of all, do you need multibyte character set support? If no, please use c/ODBC 3.51. If yes, please attach ODBC trace of the problem and I'll try figuring out what's happening from there.

c/ODBC 5.1 is following ODBC standards much more closely than 3.51 does so it might be that it's just too compliant comparing to PowerBuilder.

First of all i want to say thanks for the response, and i don't really need Multibyte character set support and i'm still using 3.51 version.  I only think that it would be nice to use the newest ODBC, but i guess newer doesn't always means better.

Well, newer connector in this case is much more strict regarding ODBC specifications. Whether this is bad or good, I can't tell.

Now, I still need ODBC traces if you want to proceed with checking.

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

I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.