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.

Bug 156680

Summary:	Connection isn't added adter clicking "OK" button if fields aren't synchronized
Product:	db	Reporter:	Roman Mostyka <romanmostyka>
Component:	Code	Assignee:	Jiri Rechtacek <jrechtacek>
Status:	RESOLVED FIXED
Severity:	blocker	Keywords:	UI
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Bug Depends on:
Bug Blocks:	152580

Description Roman Mostyka 2009-01-13 13:35:14 UTC

1. Rightclick "Databases" node and choose "New Connection".
2. Enter all necessary information and check "Show JDBC URL" checkbox.
3. Change something (for example DB name) and click "OK" button.

Result: Nothing happens, new connection isn't added. Only value in "Database" field was synchronized. But when user
clicks "OK" button it is expected that new connection will be added. But for adding connection now user has to click
"OK" button second time. We should avoid such redundant actions, one click should be enough for synchronizing and adding
of the new connection.

Comment 1 Jiri Rechtacek 2009-02-10 15:28:22 UTC

Reassigned to new owner.

Comment 2 Jiri Rechtacek 2009-02-24 14:02:21 UTC

Quoted from issue 156682:
1. Rightclick "Databases" node and choose "New Connection".
2. Enter all necessary information and check "Show JDBC URL" checkbox.
3. Select "Direct URL Entry" radiobutton and change something (for example DB name).
4. Select "Field Entry" radiobutton.

Result: DB name hasn't been changed, so "Field Entry" isn't in sync with "Direct URL Entry".

5. Select "Direct URL Entry" radiobutton.

Result: Changed DB name is the same as it was before step 3.

Comment 3 Jiri Rechtacek 2009-02-24 14:03:01 UTC

*** Issue 156682 has been marked as a duplicate of this issue. ***

Comment 4 Jiri Rechtacek 2009-07-01 07:43:59 UTC

NB6.7 was released already - http://www.netbeans.org/community/releases/67/
Postpone fixing this issue on the next release.

Comment 5 Jiri Rechtacek 2010-01-06 03:45:50 UTC

No more reproducible. Fixed probably while stabilization NB6.8.