Bug #68817 | mysqlslap documentation badly flawed/incomplete | ||
---|---|---|---|
Submitted: | 29 Mar 2013 23:40 | Modified: | 1 Apr 2013 19:58 |
Reporter: | Kolbe Kegel | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.5.30 | OS: | Any |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | mysqlslap |
[29 Mar 2013 23:40]
Kolbe Kegel
[1 Apr 2013 14:46]
MySQL Verification Team
Seems like the fix for http://bugs.mysql.com/bug.php?id=58090 meant to add this, but that changeset didn't really!
[1 Apr 2013 16:01]
Nirbhay Choubey
Looks like the previous (unapproved) version of the committed patch was referenced to produce the docs' changelog. The approved patch that actually went into the main code introduced --no-drop (as rightly pointed by Kolbe) : http://lists.mysql.com/commits/134382
[1 Apr 2013 19:51]
Paul DuBois
Corrected changelog entry for Bug#58090: When invoked with the --auto-generate-sql option, mysqlslap dropped the schema specified with the --create-schema option at the end of the test run, which may have been unexpected by the user. mysqlslap now has a --no-drop option that prevents any schema created during the test run from being dropped.
[1 Apr 2013 19:58]
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. Kolbe, good catch!