MySQL Bugs: #32313: ODBC driver resets TEXT field

Bug #32313	ODBC driver resets TEXT field
Submitted:	13 Nov 2007 12:22	Modified:	13 Nov 2007 12:31
Reporter:	Peter Reinhold	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.21.00	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	BLOB, null, ODBC, text

Description:
I just upgraded from ODBC 3.51.12 to 3.51.21 (Yes, it's been a while, but i've had no reason to upgrade before now)

Immidiately after upgrading, I started experiencing errors on scripts that worked fine before, and I have boiled it down to the following.

When I retrieve the value of a TEXT field (haven't tried with a BLOB) from an ADO recordset, the value is reset to NULL, and I can't work with it again.

Process was, I tested if the TEXT field was NULL, and reacted accordingly, now I had to change it to extracting the TEXT value to a variable, and work on that instead, testing if it is NULL by seeing if the value has length 0.

How to repeat:
Retrieve a TEXT field into a RecordSet using ADO, and then try retrieving the value from the recordset twice.

First time it returns the value, next time it returns NULL

Suggested fix:
No idea

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Explanation: Hi Peter and thanks for your report. This is a duplicate of Bug#31029 and, in turn, many others. Please follow the discussion from there.