MySQL Bugs: #49297: WB is unaware of import failures

Bug #49297	WB is unaware of import failures
Submitted:	1 Dec 2009 20:48	Modified:	17 Dec 2009 15:27
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.10 r4680	OS:	Windows (XP)
Assigned to:	Alexander Musienko	CPU Architecture:	Any

Description:
When importing a data export file, I could not find that it had succeeded by inspecting my database.  The table did not exist after the import had supposedly finished, with the following entry in the log:

12:32:50 Import has finished

I believe the root cause was related to Bug #49295, where it was attempting to execute the import against my local machine instead of the remote machine using TCP/IP over SSH.

However, regardless of the *cause* of failure, the fact that WB is apparently unaware of success or failure, and does not alert the user to the same, is particularly troublesome.

I was able to further repeat this by manually editing the .SQL file I was attempting to import to add statements that should explicitly fail:

COMPLETE FAIL;

And WB, upon importing this file again, continued to insist that the import was complete.

How to repeat:
See above.

Suggested fix:
WB needs to be aware of, and alert the user to, success and failure conditions in handling data imports.

fixed in repository.
will be included in 5.2.11

An entry has been added to the 5.2.11 changelog:

When importing data via the Data Dump tab of the Admin screen, MySQL Workbench did not notify the user of failed imports, because it could not detect failed imports.