MySQL Bugs: #77835: mysqlpump --help provides no invocation syntax

Bug #77835	mysqlpump --help provides no invocation syntax
Submitted:	25 Jul 2015 16:08	Modified:	18 Aug 2015 13:38
Reporter:	Paul DuBois	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S3 (Non-critical)
Version:	5.7.8, 5.7.9	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
mysqldump --help provides program purpose and invocation syntax:

Dumping structure and contents of MySQL databases and tables.
Usage: mysqldump [OPTIONS] database [tables]
OR     mysqldump [OPTIONS] --databases [OPTIONS] DB1 [DB2 DB3...]
OR     mysqldump [OPTIONS] --all-databases [OPTIONS]

mysqlpump --help does not. So it's not clear at all from the help message how to use the program.

Secondary issue: mysqldump --help and mysqlpump --help are inconsistent about where in the help message the information about option files is located. For mysqldump, it appears before the list of options. For mysqlpump, it appears after. This is actually a general problem among MySQL client programs, which are inconsistent about the order in which they execute these two functions when printing the help message:

  my_print_help(my_long_options);
  my_print_variables(my_long_options);

I guess mysqlpump doesn't use those functions (?) but programs should still print sections of the help message in consistent order.

How to repeat:
Invoke:

mysqlpump --help

Compare to:

mysqldump --help

Suggested fix:
Print program purpose and invocation syntax in the help message.

Secondary issue: MySQL programs should print sections of the help message in a consistent order.

Hello Paul,

Thank you for the bug report.
Verified as described with 5.7.9 builds.

Thanks,
Umesh

Fixed in 5.7.9. Cosmetic change. No changelog entry needed.