Bug #5655 mysqldump fields-escaped-by behaviour
Submitted: 19 Sep 2004 19:46 Modified: 23 Sep 2004 13:39
Reporter: Nick Lott Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: mysqldump Command-line Client Severity:S3 (Non-critical)
Version:4.0.18 OS:Linux (Fedora Core 2)
Assigned to: Antony Curtis CPU Architecture:Any

[19 Sep 2004 19:46] Nick Lott
Description:
Maybe I'm just being particularly dense tonight, but if this isn't a bug the behaviour differs from the documentation.

using:
mysqldump  Ver 9.10 Distrib 4.0.18, for pc-linux (i686)

The following command:
mysqldump --tab=/tmp --fields-terminated-by=';' --fields-enclosed-by='"' --fields-escaped-by='\\' --lines-terminated-by='\r\n' database table

gives the error:
mysqldump: option '--fields-escaped-by' cannot take an argument

The only way round it is to use SELECT ... INTO OUTFILE

How to repeat:
Run this:
mysqldump --tab=/tmp --fields-terminated-by=';' --fields-enclosed-by='"' --fields-escaped-by='\\' --lines-terminated-by='\r\n' database table

Suggested fix:
Either --fields-escaped-by should take an argument or the man page/online documentation should be changed to match the actual behaviour of this command.
[19 Sep 2004 21:44] MySQL Verification Team
Tested against BK source 4.0 on Linux. The binary from BK source 4.1 was able
to perform the statement reported.
[22 Sep 2004 10:29] Antony Curtis

 
[23 Sep 2004 13:39] Antony Curtis
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