Bug #81789 Workbench throws unexpected error while deleting rows
Submitted: 9 Jun 2016 16:48 Modified: 13 Jun 2016 8:02
Reporter: Pradeep Jeyajothiraj Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.2 OS:Windows (8.1)
Assigned to: CPU Architecture:Any
Tags: MySQL Workbench

[9 Jun 2016 16:48] Pradeep Jeyajothiraj
I had two tables having ID as primary key column.  Have added foreign key in the second table with option on delete as cascade.  When I try to delete a row from workbench UI (not query), it deletes the row but it shows a pop-up and asks me to report it.

My explanation might not be sufficient as I am not a developer, I can share the screenshot if that helps you.

How to repeat:
as mentioned above
[9 Jun 2016 16:50] Pradeep Jeyajothiraj
Added screenshot as well
[9 Jun 2016 17:07] MySQL Verification Team
Please try version 6.3.6. Thanks.
[10 Jun 2016 18:46] Pradeep Jeyajothiraj
Installed 6.3.6 64 bit, it didnt start at all.   After some googling installed 32 bit though my windows is 64 bit, it starts but keeps throwing 2013 and 2006 error, unable to check now.
[11 Jun 2016 4:54] MySQL Verification Team
Thank you for the heads up.
Did you install MySQL Workbench Prerequisites?
To be able to install and run MySQL Workbench your System needs to have libraries listed below installed. The listed items are provided as links to the corresponding download pages where you can fetch the necessary files.

- Microsoft .NET Framework 4 Client Profile
- Visual C++ Redistributable for Visual Studio 2013

Please see https://dev.mysql.com/downloads/workbench/
[11 Jun 2016 5:22] Pradeep Jeyajothiraj
It seems that I have all those libraries but still I was getting the popular DLL missing error.  I somehow managed to get rid of 2006 error and the delete does not throw the same error now.  Probably this was a problem in 6.2 workbench then.  I hope this bug can be closed as you wish.
[13 Jun 2016 8:02] MySQL Verification Team
Thank you for confirming Pradeep.
Closing the bug report for now.