Bug #44412 mysqlslap ignores --csv flag without a filename

Description:
Per the man pages:

--csv[=file_name]

Generate output in comma-separated values format. The output goes to the named file, or to the standard output if no file is given. This option was added in MySQL 5.1.5. 

Yet it produces normally formatted results with just the --csv parameter passed in. 

How to repeat:
 mysqlslap  -uroot -p -a -i 1 --csv

On my machine this produces:

 $ mysqlslap  -uroot -p -a -i 1 --csv 
Enter password: 
Benchmark
	Average number of seconds to run all queries: 0.004 seconds
	Minimum number of seconds to run all queries: 0.004 seconds
	Maximum number of seconds to run all queries: 0.004 seconds
	Number of clients running queries: 1
	Average number of queries per client: 0

However with --csv=mytest.csv, the file mytest.csv looks like this:
philip@sonny ~ $ mysqlslap  -uroot -p -a -i 1 --csv=mytest.csv
Enter password: 
philip@sonny ~ $ cat mytest.csv 
,mixed,0.004,0.004,0.004,1,0

Suggested fix:
Make the option write csv to standard out when no file name provided, per documentation. Helpful for scripting.

Thank you for the bug report. Verified as described.

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/74439

2900 Jim Winstead	2009-05-18
      mysqlslap didn't correctly handle --csv with no argument. (Bug #44412)
      modified:
        client/mysqlslap.c

Pushed to 5.1-bugteam and mysql-pe.

Pushed into 5.4.4-alpha (revid:alik@sun.com-20090804194615-h40sa098mx4z49qg) (version source revid:jimw@mysql.com-20090714171651-ziq080rkon3u244l) (merge vers: 5.4.4-alpha) (pib:11)

Pushed into 5.1.38 (revid:davi.arnaut@sun.com-20090804204317-ggodqkik7de6nfpz) (version source revid:davi.arnaut@sun.com-20090804204317-ggodqkik7de6nfpz) (merge vers: 5.1.38) (pib:11)

Noted in 5.1.38, 5.4.4 changelogs.

mysqlslap ignored the --csv option if it was given without an
argument.

Noted in 5.4.2 changelog because next 5.4 version will be 5.4.2 and not 5.4.4.

Ignore previous comment about 5.4.2.

Pushed into 5.1.39-ndb-6.3.28 (revid:jonas@mysql.com-20091001055605-ap2kiaarr7p40mmv) (version source revid:jonas@mysql.com-20091001055605-ap2kiaarr7p40mmv) (merge vers: 5.1.39-ndb-6.3.28) (pib:11)

Pushed into 5.1.39-ndb-7.0.9 (revid:jonas@mysql.com-20091001072547-kv17uu06hfjhgjay) (version source revid:jonas@mysql.com-20091001071652-irejtnumzbpsbgk2) (merge vers: 5.1.39-ndb-7.0.9) (pib:11)

Pushed into 5.1.39-ndb-7.1.0 (revid:jonas@mysql.com-20091001123013-g9ob2tsyctpw6zs0) (version source revid:jonas@mysql.com-20091001123013-g9ob2tsyctpw6zs0) (merge vers: 5.1.39-ndb-7.1.0) (pib:11)

Pushed into 5.1.39-ndb-6.2.19 (revid:jonas@mysql.com-20091005103850-dwij2dojwpvf5hi6) (version source revid:jonas@mysql.com-20090930185117-bhud4ek1y0hsj1nv) (merge vers: 5.1.39-ndb-6.2.19) (pib:11)

The 5.4 fix has been pushed to 5.4.2.