Bug #1749 | Prepared statements within transaction | ||
---|---|---|---|
Submitted: | 4 Nov 2003 12:54 | Modified: | 20 Jan 2004 22:13 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.1 alpha | OS: | Windows (win 2k) |
Assigned to: | Alexey Botchkov | CPU Architecture: | Any |
[4 Nov 2003 12:54]
[ name withheld ]
[4 Nov 2003 13:56]
Heikki Tuuri
Hi! Yes, prepare/execute with InnoDB is badly broken in 4.1.0, because MySQL changes thd->query_id differently from field->query_id in execute() (or was it in prepare()?). The rule is that InnoDB should fetch those fields where thd->query_id == field->query_id. But the current MySQL code fails to keep the id's right. Regards, Heikki
[20 Jan 2004 22:13]
Alexey Botchkov
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: Fixed with the big cleanup()-related patch