Bug #17455 | Partitions: OPTIMIZE/REPAIR TABLE,wrong message + warnings depending on engine | ||
---|---|---|---|
Submitted: | 16 Feb 2006 13:56 | Modified: | 31 May 2006 4:57 |
Reporter: | Matthias Leich | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Partitions | Severity: | S3 (Non-critical) |
Version: | 5.1 | OS: | |
Assigned to: | Mikael Ronström | CPU Architecture: | Any |
[16 Feb 2006 13:56]
Matthias Leich
[16 Feb 2006 13:57]
Matthias Leich
testcase
Attachment: ml102.test (application/test, text), 388 bytes.
[24 May 2006 11:52]
Mikael Ronström
Reviewed by Sergey Gluhov
[26 May 2006 17:21]
Mikael Ronström
Will appear in version 5.1.12
[30 May 2006 7:31]
Mikael Ronström
I think the behaviour now follows the normal reporting behaviour of non-partitioned tables although of course you can get reports on many partitions in one command and not on just one table.
[31 May 2006 4:57]
Jon Stephens
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: Documented bugfix in 5.1.12 changelog. Closed.