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.
Summary: | The IDE freezes for half a minute if incorrect data are entered in Add Connection | ||
---|---|---|---|
Product: | db | Reporter: | iformanek <iformanek> |
Component: | Code | Assignee: | issues@db <issues> |
Status: | VERIFIED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
iformanek
2003-07-10 14:37:29 UTC
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 |