Bug #13047 | mysqldump --skip-quote-names does not work | ||
---|---|---|---|
Submitted: | 7 Sep 2005 19:21 | Modified: | 9 Sep 2005 18:00 |
Reporter: | Patrick Lum | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 4.1.14-standard | OS: | Linux (RH Enterprise 3) |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[7 Sep 2005 19:21]
Patrick Lum
[7 Sep 2005 22:33]
Hartmut Holzgraefe
the backtick quotes are added if either the --allow-keywords or --quote-names option is active, you have used the --skip-quote-names but due to the use of --allow-keywords option quotes are still added this is not really clear from the documentation so i changed this to a documentation issue ...
[8 Sep 2005 13:43]
Patrick Lum
No, that didn't work. I am trying: $ mysqldump -u root -p --all-databases --add-drop-table --skip-quote-names --compatible='mysql323' > mysql3_dump $ head -100 mysql3_dump | grep "CREATE TABLE" CREATE TABLE `columns_priv` ( CREATE TABLE `db` ( CREATE TABLE `func` (
[8 Sep 2005 16:47]
Jani Tolonen
Option --compatible=... implicitely sets --quote-names on. It can be forced to not quote names by adding --skip-quote-names *after* --compatible=... option. However, MySQL 3.23 is capable of reading output with quoted names, also mysqldump in release 3.23 is capable of producing quoted output. (Tested with 3.23.59) Are you having problems with using output with quoted names?
[9 Sep 2005 13:01]
Patrick Lum
Thanks, that worked! Version 3.23.58 does not understand quoted names.
[9 Sep 2005 18:00]
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 product(s). Additional info: I'll add a note that --skip-quote-names has to be given after --compatible or it will have no effect.