Bug #6600 | Stored procedure crash after repeated calls with check table | ||
---|---|---|---|
Submitted: | 12 Nov 2004 19:58 | Modified: | 31 Mar 2005 9:46 |
Reporter: | Peter Gulutzan | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.2-alpha-debug | OS: | Linux (SuSE 8.2) |
Assigned to: | Per-Erik Martin | CPU Architecture: | Any |
[12 Nov 2004 19:58]
Peter Gulutzan
[18 Mar 2005 16:10]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/23178
[18 Mar 2005 16:20]
Per-Erik Martin
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
[30 Mar 2005 11:28]
Per-Erik Martin
Reopening, since it turned out tha the fix was incorrect.
[30 Mar 2005 16:03]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/23496
[10 May 2006 19:44]
Harri Sylvander
You might want to update the documentation to reflect this change. Documentation on stored routines' restrictions still says restrictions on CHECK TABLES and OPTIMIZE TABLES was lifted in 5.0.17. Sincerely, Harri Sylvander