Red Hat Bugzilla – Bug 828942
when the schema table tree is expanded, clicking on a dropped table that had a foreign key constraint makes program crash
Last modified: 2012-09-12 10:57:58 EDT
Description of problem:
On the left side, expand out the tables item on a given schema. then issue a drop table sql statement to drop one of the tables. Then click on that table from the tree on the left and application crashes. This ONLY happens when the dropped table has a foreign key constraint.
Tables without foreign keys don't do this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.expand out the schema from the tree on the left
2.expand out the tables item
3.create a table that has a foreign key to another table
4.refresh the schema so this new table shows up under the tables item
5.issue a drop table command to drop this newly created table.
6.click on said table from the tables item.
I swapped out the schema and table names with <schema name> and <table name>, respectively.
mysql workbench starts with the following scrolling in a terminal, until it finally segfaults:
** (mysql-workbench-bin:28969): WARNING **: Error fetching foreign key information for '<schema name>'.'<table name>': Table '<schema name>.<table_name>' doesn't exist
** (mysql-workbench-bin:28969): WARNING **: Error fetching index information for '<schema name>'.'<table name>': Table '<schema name>.<table_name>' doesn't exist
The program not to crash. An error message or something indicating that the table doesn't exist anymore would be better than crashing.
I tested it out on Fedora 16,
And on Fedora 17,
with the same results.
I changed the version from 15 to 16.
Please update to 5.2.40 which is un updates-testing and should be soon in updates
Please update to 5.2.42
I've updated to 5.2.42, and I believe this problem has been fixed.
Version 5.2.42 also started crashing a lot. I started running into problems with creating connections, as documented in this bug, https://bugzilla.redhat.com/show_bug.cgi?id=854994
> I've updated to 5.2.42, and I believe this problem has been fixed.
So,I close this one.