MySQL Bugs: #73551: Docs: --regexp for mysqldbcompare documented but not implemented

Bug #73551	Docs: --regexp for mysqldbcompare documented but not implemented
Submitted:	12 Aug 2014 17:26	Modified:	13 Oct 2014 20:19
Reporter:	Leandro Morgado	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Utilities	Severity:	S3 (Non-critical)
Version:	1.4.4	OS:	Linux
Assigned to:	Chuck Bell	CPU Architecture:	Any

Description:
The MySQL Utilities manual has this entry:
====
" --regexp, --basic-regexp, -G

Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching."
http://dev.mysql.com/doc/mysql-utilities/1.4/en/mysqldbcompare.html#option_mysqldbcompare_...
====

However, the mysqldbcompare binary doesn't actually recognize the option:
====
shell> mysqldbcompare. --regexp
Usage: mysqldbcompare --server1=user:pass@host:port:socket --server2=user:pass@host:port:socket db1:db2

mysqldbcompare: error: no such option: --regexp
====

How to repeat:
shell> mysqldbcompare  --help | head -n2
MySQL Utilities mysqldbcompare version 1.4.4 (part of MySQL Workbench Distribution 6.1.4) 
License type: GPLv2    

shell>  mysqldbcompare  --help | grep -i regexp

shell> mysqldbcompare --regexp
Usage: mysqldbcompare --server1=user:pass@host:port:socket --server2=user:pass@host:port:socket db1:db2

mysqldbcompare: error: no such option: --regexp

shell> mysqldbcompare -G
Usage: mysqldbcompare --server1=user:pass@host:port:socket --server2=user:pass@host:port:socket db1:db2

mysqldbcompare: error: no such option: -G

Suggested fix:
Make documented options for mysqldbcompare consistent with the ones actually implemented by the binary. Please double check mysqldbcompare --help is also consistent.

Fixed category, since this is now apparently being handled as a software issue.

Posted by developer:
 
Fixed as of the upcoming MySQL Utilities 1.5.3 release, and here's the changelog entry:

The "mysqldbcompare" utility options related to comparing all databases on
two servers were accidentally removed (e.g., "--all", "--exclude", and
"--regexp" in a previous release, and they have since been restored.

Additionally, error handling and validation routines were
improved.

Thank you for the bug report.