Bug #6996 | Prepared Statements: mysql_stmt_data_seek(stmt, 0) doesn't function properly | ||
---|---|---|---|
Submitted: | 3 Dec 2004 18:41 | Modified: | 7 Dec 2004 17:24 |
Reporter: | Timothy Smith | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 4.1.7 | OS: | Any (all) |
Assigned to: | CPU Architecture: | Any |
[3 Dec 2004 18:41]
Timothy Smith
[7 Dec 2004 10:49]
Daniel Muench
The bug is in mysql_stmt_fetch: There you set stmt->read_row_func= stmt_read_row_no_data; if read_row_func returns MYSQL_NO_DATA But if you have a buffered result set, there is no chance to read from it again after this call - even if you call mysql_stmt_data_seek() It is also marked with a /* XXX: this is buggy */ so I guess you already know where the failure is (:
[7 Dec 2004 17:24]
MySQL Verification Team
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: ChangeSet: 1.2142 in MySQL 4.1.8