MySQL Bugs: #4212: ODBC 3.51.07 max(date) column does not return proper date data

Bug #4212	ODBC 3.51.07 max(date) column does not return proper date data
Submitted:	18 Jun 2004 21:13	Modified:	28 Jul 2004 23:10
Reporter:	Matt Ryan	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.15.07	OS:	Windows (windows 2000)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
SELECT DOC_NO, FY, APC, SUM(AMOUNT) AMT_DISB, MAX(DATE) DTE_DISB FROM NXG 
WHERE TA IN ('29','40','41','42','44') GROUP BY DOC_NO, APC, FY

max(date) will not return a proper date, foxpro pics it up as a memo field, previous versions came in as a proper date field

I will try to develop a test table & case, however first try did not work, ms query picks it up as a date?!?!

Possible foxpro+mysql bug only

How to repeat:
Working on it!

To create test table

CREATE TABLE `table1` (
  `c1` char(4) default NULL,
  `c2` char(1) default NULL,
  `c3` decimal(11,2) default NULL,
  `d1` date default NULL
) TYPE=MyISAM;

INSERT INTO `table1` VALUES ('cda','c','5.00','2004-06-18'),('cda','b','10.00','2004-06-18');

To display bug in foxpro

create dsn

in foxpro command window execute

LNHANDLE=SQLCONNECT('dsn that was created')
VALSQL="SELECT c1, c2, MAX(d1) dte FROM table1 group by c1, c2"
LNRES=SQLEXEC(LNHANDLE,VALSQL,'testarr')
BROWSE

dte will show up in a memo format, 3.51.06 showed it in a date format

Hello!  Thanks for your bug report.  This looks like the same problem as bug #4578.  Can you please try MyODBC 3.51.9 when it is released, and let us know here if it does not fix your problem.

Thanks,

Timothy