Bug #31022 | MyODBC higher than 3.51.12 returns empty columns | ||
---|---|---|---|
Submitted: | 14 Sep 2007 7:50 | Modified: | 8 Oct 2007 12:44 |
Reporter: | Jerry Potokar | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Connector / ODBC | Severity: | S1 (Critical) |
Version: | 3.14 and later | OS: | Windows (Windows 2003) |
Assigned to: | CPU Architecture: | Any |
[14 Sep 2007 7:50]
Jerry Potokar
[14 Sep 2007 8:11]
Jerry Potokar
Here is a test code: <%@LANGUAGE="VBSCRIPT"%> <!--#include file="Connections/xy.asp" --> <% Dim rsTest Dim rsTest_cmd Dim rsTest_numRows Set rsTest_cmd = Server.CreateObject ("ADODB.Command") rsTest_cmd.ActiveConnection = MM_xy_STRING rsTest_cmd.CommandText = "SELECT * FROM xy.test" rsTest_cmd.Prepared = true Set rsTest = rsTest_cmd.Execute rsTest_numRows = 0 %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>Untitled Document</title> </head> <body> <p><%=(rsTest.Fields.Item("xy").Value)%></p> <p> </p> <p><%=(rsTest.Fields.Item("xy").Value)%> </p> </body> </html> <% rsTest.Close() Set rsTest = Nothing %> Here is the connect string: Dim MM_xy_STRING MM_xy_STRING="Driver={MySQL ODBC 3.51 Driver};server=localhost;uid=xy;pwd=xy;database=xy;OPTION=16384;stmt=SET NAMES 'utf8'" %> The result is I loose the code after the first response.write. Second response.write is EMPTY :-( And the RS is empty after that also... It is not just response.write, even if I compare something with the recordset it looses it's value.
[14 Sep 2007 8:15]
Jerry Potokar
The most important note is this: THIS HAPPENS ON TEXT fields in database, not char, varchar or numberic. Only text firelds dissapear. 5.1 Odbc has the same problem now :-(
[8 Oct 2007 10:22]
Susanne Ebrecht
Hi Jerry, Thanks, for writing a bug report. This is a duplicate of bug #16899. Regards, Susanne
[8 Oct 2007 12:44]
Jerry Potokar
This does not seem to be the same bug to me. And your reference is said to be fixed in some early version of 3.51.12. I think this is a mistake, sorry...
[8 Oct 2007 16:48]
Susanne Ebrecht
Sorry, I missed the number ... this is a duplicate of bug #16866