MySQL Bugs: #70926: error from mysqldbcompare

Bug #70926	error from mysqldbcompare
Submitted:	15 Nov 2013 18:22	Modified:	19 Dec 2013 15:39
Reporter:	Wendy Tao	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Utilities	Severity:	S3 (Non-critical)
Version:	mysqluc V1.3.5	OS:	Windows (Windows 7)
Assigned to:		CPU Architecture:	Any
Tags:	mysqldbcompare

Description:
Received error when performing mysqldbcompare (See details in private comments.)

ERROR: The object definitions do not match.
An error was found, while executing the command, use "show last error" command t
o display details

mysqluc> show last error
Execution of utility: mysqldbcompare --server1=root:mysql0000@pdb-k-linux-14.rut
gers.edu kbdbv1:kbdbv1_copy_k13
returned errorcode: 1 and no error message

mysqluc>

How to repeat:
I can provide database dump file if needed.

Please provide the dump file. Thanks.

If the only thing you saw was the difference in the table name, you're Ok. The message about an error is actually from the mysqluc. If you immediately issue SHOW LAST ERROR in mysqluc, it will show the return code.

Now, try running mysqldbcompare outside of mysqluc. You will see the same messages except for the bit about SHOW LAST ERROR. 

This is by design. The mysqluc cannot know what the last error was and in the case of when there are differences (when running mysqldbcompare), the return code is non-zero (-1 in this case) but there may not be an error. This is so that you can use mysqldbcompare in a script and check its return code.

Thus, unless there are other errors, this isn't a defect.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".