Bug #26077 | 'reap' command fetches first command issued by send, not the most recent | ||
---|---|---|---|
Submitted: | 5 Feb 2007 9:13 | Modified: | 30 Jun 2009 20:34 |
Reporter: | Giuseppe Maxia | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.1.15 | OS: | Linux (Linux,Mac OSX) |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | Docs, server, Tests |
[5 Feb 2007 9:13]
Giuseppe Maxia
[15 May 2009 20:41]
Jim Winstead
It has been suggested (in a private comment) that the proper fix for this is to prevent, in the C API, a query from being sent before the results of the previous query have been handled, which is why the bug is in the C API category and triaged as it is.
[16 Jun 2009 16:52]
Jim Winstead
And we're not going to make that change. This is purely a documentation problem, as noted in the original report.
[30 Jun 2009 20:34]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. I will avoid "first" and "most recent" altogether and emphasize that there should be only one send at a time: Receive the result of the statement sent with the send command within the current session. You should not use reap unless a statement has been sent with send, and you should not use send again if there is an outstanding send that has not been processed with reap.