Bug #20070 | do not require mysql_next_result() to be called for update/insert/etc. | ||
---|---|---|---|
Submitted: | 25 May 2006 18:10 | Modified: | 26 Jul 2006 22:49 |
Reporter: | Timothy Smith | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.0.22 | OS: | Linux (linux, freebsd, any) |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[25 May 2006 18:10]
Timothy Smith
[25 May 2006 18:17]
Timothy Smith
Test program
Attachment: mult_update.c (application/octet-stream, text), 2.39 KiB.
[25 May 2006 18:34]
Timothy Smith
See also bug #20072; fixing it may also fix this one.
[22 Jul 2006 16:07]
Timothy Smith
Magnus, After reviewing this, I think you're right and it just needs to be documented properly that mysql_next_result() *must* be called any time there are multiple statements, regardless of the content of those statements. In particular, the following passage is misleading: http://dev.mysql.com/doc/refman/5.0/en/c-api-multiple-queries.html "By default, mysql_query() and mysql_real_query() return only the first query status and the subsequent queries status can be processed using mysql_more_results() and mysql_next_result()." And, I would want a single sentence on the following pages stating that if more results exist, then mysql_next_result() *must* be called: http://dev.mysql.com/doc/refman/5.0/en/mysql-next-result.html http://dev.mysql.com/doc/refman/5.0/en/mysql-more-results.html Regards, Timothy
[26 Jul 2006 22:49]
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.