Bug #4264 | when | ||
---|---|---|---|
Submitted: | 23 Jun 2004 19:47 | Modified: | 24 Oct 2005 20:31 |
Reporter: | bill zheng | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51 | OS: | Windows (windows 2000) |
Assigned to: | Peter Harvey | CPU Architecture: | Any |
[23 Jun 2004 19:47]
bill zheng
[31 Aug 2004 22:00]
MySQL Verification Team
Thank you for the bug report: mysql> select * from tbl_test; +---------+-------+----------+ | typeid_ | type_ | typeabr_ | +---------+-------+----------+ | 0 | NULL | NULL | | 30 | aa | bb | +---------+-------+----------+ 2 rows in set (0.00 sec)
[28 Sep 2004 2:41]
Jeff Martin
I just logged bug #5778. I'll bet that the root cause of this bug (#4364) is that the Perl DBI for ODBC always calls the ODBC function SQLNumResultCols() after every SQLPrepare(). Bug #5778 demonstrates that this combination results in an extra "blank" row inserted into the table.
[12 Apr 2005 2:01]
Peter Harvey
This is probably a result of a prepared INSERT being silently executed so as to determine Rows/Cols. This has been address and I beleive in the current distro (MyODBC 3.51.11).
[24 Oct 2005 20:31]
Peter Harvey
Fixed in c/odbc v3.51.11 (fix also in v3.51.12 etc).