Bug #35224 mysqldump --help is very confusing
| Submitted: | 11 Mar 2008 16:07 | Modified: | 6 Mar 2010 23:21 |
|---|---|---|---|
| Reporter: | Susanne Ebrecht | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: mysqldump Command-line Client | Severity: | S3 (Non-critical) |
| Version: | 5.1-bk | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[11 Mar 2008 17:49]
Chad MILLER
patch and example output
Attachment: p35224 (application/octet-stream, text), 17.01 KiB.
[12 Mar 2008 18:58]
Jim Winstead
please have someone in docs review the added text to make sure they are happy with it.
[12 Mar 2008 20:07]
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/commits/43879 ChangeSet@1.2601, 2008-03-12 16:06:07-04:00, cmiller@zippy.cornsilk.net +3 -0 Bug#35224: mysqldump --help is very confusing The presence of "--skip" parameters is obscure, when it should be obvious from the text. Now, for boolean options, when they're default to ON and the --skip is more useful parameter, then tell the user of its existence.
[14 Mar 2008 16:01]
Chad MILLER
Queued to 6.0-build.
[28 Mar 2008 11:10]
Bugs System
Pushed into 6.0.5-alpha
[22 Apr 2008 18:10]
Paul DuBois
Noted in 6.0.5 changelog. For boolean options, the option-processing library now prints additional information in the --help message: If the option is enabled by default, the message says so and indicates that the --skip form of the option disables the option. This affects all compiled MySQL programs that use the library.
[3 Nov 2009 9:23]
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/commits/89047 2904 Magne Mahre 2009-11-03 Bug#35224: mysqldump --help is very confusing The presence of "--skip" parameters is obscure, when it should be obvious from the text. Now, for boolean options, when they're default to ON and the --skip is more useful parameter, then tell the user of its existence. Backported from 6.0-codebase, revid 2572.14.1
[3 Nov 2009 9:24]
Magne Mæhre
Backported to next-mr-runtime (5.5.0)
[20 Nov 2009 12:57]
Bugs System
Pushed into 6.0.14-alpha (revid:kostja@sun.com-20091120124947-yi6h2jbgw0kbciwm) (version source revid:jon.hauglid@sun.com-20090928163426-2lg1gofzz44xzzxf) (merge vers: 6.0.14-alpha) (pib:13)
[26 Nov 2009 15:24]
Paul DuBois
Already fixed in 6.0.x. Setting report to NDI pending push to 5.5.x (5.6.x?)
[6 Mar 2010 11:07]
Bugs System
Pushed into 5.5.3-m3 (revid:alik@sun.com-20100306103849-hha31z2enhh7jwt3) (version source revid:jon.hauglid@sun.com-20090928163426-2lg1gofzz44xzzxf) (merge vers: 6.0.14-alpha) (pib:16)
[6 Mar 2010 23:21]
Paul DuBois
Noted in 5.5.3 changelog.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.046 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
Description: I wanted a mysqldump with separate insert statements for every row. $ mysqldump --help ... -e, --extended-insert Allows utilization of the new, much faster INSERT syntax. ... Ok, this means without -e it won't make the "new" INSERT syntax. $ mysqldump mydb.testdb > foo Result: Also without the "-e" it takes the "new" INSERT syntax. I figured out that I need: --skip-extended But this isn't documented at mysqldump --help How to repeat: $ mysqldump --help Suggested fix: Add documentation for mysqldump --skip-extended Add a sentense that "this is default behaviour" at -e