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.
Using MySQL driver, if I enter a connection to host that is not accessible (e.g. bcs of firewall), the IDE freezes for about 30 seconds when I click Advanced tab or OK in the Add Connection dialog. Perhaps this task should not be done in AWT thread? Also, it does not seem to be possible to add a connection that at the moment does not work, should this be allowed? I assume temporarily non-working connections can exist in the explorer, such as in case when I add a working connection and then remove Ethernet cable, the connection would remain in the explorer as broken, right?
The first part (connect in non-AWT thread) duplicates #28199. It is mostly done and will be commited soon. It is not allowed to add connection for non-running database - if we allow to connect to running database only, we can check all connection arguments and say the user which argument is wrong. This would not be possible fot non-running databases. *** This issue has been marked as a duplicate of 28199 ***
Hmm, yes and no. Although you can assess the accuracy of the data with live database, it has no guarantee to remain valid if the database changes. I.e. I can again end up in a state where the connection is invalid, and the case needs to be handled. Allowing to add invalid connection (invalid as "the database cannot be connected" or "the data are invalid") would still IMO make sense, if a warning is displayed. Enforcing live connection is too restrictive in my opinion.
VERIFIED