This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Build: NetBeans IDE Dev (Build 091006) VM: Java HotSpot(TM) Client VM, 14.0-b12, Java(TM) SE Runtime Environment, 1.6.0_14-ea-b03 OS: Linux, 2.6.28-15-generic, i386 User Comments: jrechtacek: When deleting bunch of tables in MySQL connection. Stacktrace: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'zrus.tab116' doesn't exist at sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:0) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.Util.getInstance(Util.java:381)
Created attachment 88989 [details] stacktrace
Let's wait for more reports.
Build: NetBeans IDE Dev (Build 200910071536) VM: Java HotSpot(TM) 64-Bit Server VM, 14.1-b02-90, Java(TM) SE Runtime Environment, 1.6.0_15-b03-219 OS: Mac OS X, 10.6.1, x86_64 User Comments: Deleting tables from mysql connection Stacktrace: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'render.user_property' doesn't exist at sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:0) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.Util.getInstance(Util.java:381)
Created attachment 89081 [details] stacktrace
*** Bug 184492 has been marked as a duplicate of this bug. ***
There are multiple nested duplicates. If the chain of duplicates is correct, then the description may have to be changed to something like: "In Database Explorer, two tables cannot be dropped at all if both have foreign key contraints referencing each other" This is a very irritating showstopper because Database explorer does not provide a means to copy the names of foreign key constraints to the clipboard. It might not be a big issue to drop constraints before dropping tables, and therefore, I change the priority to hopefully get this done in the next release.
Testcase: This is relevant for one-to-one relationships. Testcase: CREATE TABLE TABLE_1 (ID INTEGER NOT NULL, TABLE_2_ID INTEGER NOT NULL, PRIMARY KEY (ID)); CREATE TABLE TABLE_2 (ID INTEGER NOT NULL, TABLE_1_ID INTEGER NOT NULL, PRIMARY KEY (ID)); ALTER TABLE TABLE_1 ADD CONSTRAINT FK_TABLE_1_TABLE_2_ID FOREIGN KEY (TABLE_2_ID) REFERENCES TABLE_2 (ID); ALTER TABLE TABLE_2 ADD CONSTRAINT FK_TABLE_2_TABLE_1_ID FOREIGN KEY (TABLE_1_ID) REFERENCES TABLE_1 (ID); When trying to drop the tables in Database Explorer by right click|delete, the error is: Unable to execute command: drop table "APP"."TABLE_2" Operation 'DROP CONSTRAINT' cannot be performed on object 'SQL100704071938090' because CONSTRAINT 'FK_TABLE_1_TABLE_2_ID' is dependent on that object. This looks like a bug because Database Explorer seems to try to drop constraints two times. This worked as expected: ALTER TABLE TABLE_1 DROP CONSTRAINT FK_TABLE_1_TABLE_2_ID; ALTER TABLE TABLE_2 DROP CONSTRAINT FK_TABLE_2_TABLE_1_ID; DROP TABLE TABLE_1; DROP TABLE TABLE_2;
No too much duplicates, has been reported for 4 time since 6.7 release. More reports in the same issue 162530. @bth - I guess your comments are irrelevant for this issue. I filed it again as issue 192457. *** This bug has been marked as a duplicate of bug 162530 ***