MySQL Bugs: #28294: Varchar detected as Memo if Null

Bug #28294	Varchar detected as Memo if Null
Submitted:	8 May 2007 1:47	Modified:	3 Jun 2007 18:47
Reporter:	nancy turner	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	3.51.14	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Varchar fields are detected as Memo if Null.

How to repeat:
Create a table with varchar fields that have some null values.
Create System DSN using ODBC 3.51 driver
Create a Crystal Report (XI) using the DSN and select * from tablename in the command object.
Right click on the fields in the fields explorer & click display datatype.

The fields that are varchar & have a null are displayed as memo fields.
All our reports in production are failing as in Crystal Reports we cannot group by a Memo field or use a memo field in formulas

Thank you for a problem report. Please, specify the exact (3.51.xx) version of Connector/ODBC and MySQL server (5.0.xx) used.

Thank you for your response.

The server is MySQL is Version 5.0.37
The ODBC Driver is Version 3.51.14

Please note that the reports worked fine when they were running against MySQL Server 4.1.18  with ODBC 3.51.12

The issue began after we moved to Version 5.0.37

Hi Nancy. Are you sure that the problems begun after upgrading server? I think they started after upgrading MyODBC, right?

It is possible the odbc upgrade is causing the issue.
We upgraded both the server and ODBC driver. Thanks.

Nancy, I will need ODBC traces and MySQL server general query log attached (see my posts in Bug#28317). Can you please try MyODBC 3.51.15 too.

The issue was resolved - as below 

One of the fields the report was pulling was declared the type Text in the database.

Changing this to varchar(255) resolved the issue.

Nancy, thanks for your insight and feedback. I will close the report now.