| Bug #7004 | mysqldump's option --compact is missleading | ||
|---|---|---|---|
| Submitted: | 4 Dec 2004 3:48 | Modified: | 4 Dec 2004 9:05 |
| Reporter: | Jorge del Conde | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: mysqldump Command-line Client | Severity: | S3 (Non-critical) |
| Version: | 10.8 - 4.1.7 | OS: | Any (all) |
| Assigned to: | Sergei Golubchik | CPU Architecture: | Any |
[4 Dec 2004 4:35]
Paul DuBois
--skip-lock-tables does exist as an option. As usual
with --skip options, it's the "turn off" form of the
following boolean option name, in this case --lock-tables.
From mysqldump.c:
{"lock-tables", 'l', "Lock all tables for read.", (gptr*) &lock_tables,
(gptr*) &lock_tables, 0, GET_BOOL, NO_ARG, 1, 0, 0, 0, 0, 0},
[4 Dec 2004 6:23]
Jorge del Conde
In this case, lock-tables isn't working, although --skip-add-lock works fine.
[4 Dec 2004 9:05]
Sergei Golubchik
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:
fixed in 4.1.9
Description: the --compact option of mysqldump is missleading. How to repeat: --compact Give less verbose output (useful for debugging). Disables structure comments and header/footer constructs. Enables options --skip-add-drop-table --no-set-names --skip-disable-keys --skip-lock-tables but --skip-lock-tables doesn't exist as an option. --add-lock=false should be used instead.