Bug #27544 | Calling stored procedure causes "Out of sync" and "Lost connection" errors | ||
---|---|---|---|
Submitted: | 30 Mar 2007 10:01 | Modified: | 12 Jun 2007 10:26 |
Reporter: | Bogdan Degtyariov | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51 | OS: | Windows |
Assigned to: | Georg Richter | CPU Architecture: | Any |
Tags: | ODBC, stored procedure, VB |
[30 Mar 2007 10:01]
Bogdan Degtyariov
[11 Jun 2007 13:02]
Georg Richter
Fix for SQLFreeStmt: clear multi result sets
Attachment: bug27544.patch (text/x-patch), 1.64 KiB.
[11 Jun 2007 13:59]
Bogdan Degtyariov
Verified on 3.51.14/3.51.15 This bug is not present in 3.51.12
[11 Jun 2007 16:12]
Jim Winstead
Some things to fix in the patch before committing: * Add space after while in addiion to driver/handle.c * Remvoe space before = in driver/handle.c * Two blank lines before/after new test * Add header before test (see below) * Use ok_sql() instead of tmysql_exec()/mystmt(). Also eliminates need for SQLRETURN rc. /** Bug #27544: Calling stored procedure causes "Out of sync" and "Lost connection" errors */
[11 Jun 2007 17:06]
Georg Richter
committed, will appear in 3.51.16
[12 Jun 2007 10:26]
MC Brown
A note has been added to the 3.51.16 changelog.