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 150215 - Scheme can't be easily changed for added connection
Summary: Scheme can't be easily changed for added connection
Status: RESOLVED DUPLICATE of bug 197105
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All Mac OS X
: P2 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks: 152818
  Show dependency tree
 
Reported: 2008-10-15 13:01 UTC by Roman Mostyka
Modified: 2011-10-27 21:22 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Mostyka 2008-10-15 13:01:06 UTC
1. Rightclick "Databases" node and choose "New Connection...".
2. Specify parameters for the server, which has several schemes, uncheck "Remember Password" checkbox and click "OK".
3. Choose scheme in drop down list and click "OK".
4. Rightclick DB connection, choose "Properties" and click "Schemes" property.

Result: Only chosen schema is shown and there is no way to change scheme.

5. Disconnect and then reconnect to the DB.

Result: Dialog appears with prompt to enter password, but "Advanced" tab is always disabled, even after enter password
and this dialog also doesn't help to change scheme.
Customer work flow will be more flexible if it is possible to change scheme.
Only one way is to set scheme manually, but if customer doesn't know list of schemes, it is possible to look at the list
in "Advanced" tab of the "New Connection" dialog.
Comment 1 David Vancouvering 2008-10-15 18:43:18 UTC
The way we deal with schemas needs to be re-evaluated, and this is just a part of it.  

I agree it's a pain to change the schema.
Comment 2 David Vancouvering 2008-10-27 23:39:58 UTC
Will be fixed as part of our work to make schemas work better in DB Explorer
Comment 3 pgebauer 2008-11-12 18:04:24 UTC
This issue has been marked as the candidate for 65patch1 however the value "ENHANCEMENT" is stated as the issue type.
Only defects are allowed as patch candidates.

Could you please set the proper issue type value or remove the issue from the 65patch1 candidate list?
Comment 4 Roman Mostyka 2008-11-12 18:47:55 UTC
Sorry, I filed issue as a DEFECT and therefore I added status whiteboard, but then this issue was changed to be an
ENHANCEMENT.
According to desc3 this issue will be fixed as part of DB Explorer rewriting, so I agree that this issue is an
enhancement and I'll remove status whiteboard.
Comment 5 Jiri Rechtacek 2009-10-16 14:04:38 UTC
Reassigned to new owner.
Comment 6 matthias42 2011-10-27 21:22:01 UTC

*** This bug has been marked as a duplicate of bug 197105 ***