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 144112 - [65cat] Support a alias for database connection
Summary: [65cat] Support a alias for database connection
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker with 5 votes (vote)
Assignee: dynamite
Keywords: NETFIX
: 118124 150154 151466 156154 162154 166553 (view as bug list)
Depends on:
Blocks: 152816
  Show dependency tree
Reported: 2008-08-15 19:25 UTC by Michel Graciano
Modified: 2009-10-06 22:41 UTC (History)
3 users (show)

See Also:
Exception Reporter:

patch file (30.01 KB, patch)
2009-08-24 21:12 UTC, dynamite
Details | Diff
Wrong alignment on Windows JDK1.6 - Field Entry (21.98 KB, image/png)
2009-08-25 11:04 UTC, Jiri Skrivanek
Wrong alignment on Windows JDK1.6 - URL Entry (20.04 KB, image/png)
2009-08-25 11:04 UTC, Jiri Skrivanek
updated patch (59.61 KB, patch)
2009-09-06 23:24 UTC, dynamite
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2008-08-15 19:25:00 UTC
[ BUILD # : 200808141419 ]
[ JDK VERSION : 1.6.0_07 ]

Should have a alias name for database connection, which should be
used in Services view, SQL History/Command connection combobox etc.
Comment 1 David Vancouvering 2008-10-16 22:55:30 UTC
*** Issue 118124 has been marked as a duplicate of this issue. ***
Comment 2 Roman Mostyka 2008-10-17 09:33:35 UTC
*** Issue 150154 has been marked as a duplicate of this issue. ***
Comment 3 Jiri Kovalsky 2009-08-17 16:04:14 UTC
This could be a good candidate for the NetFIX team [1] - hence adding the keyword. If you are willing to implement this
take a look into Database Explorer ("db") module. You will have to alter these classes:


Plus change all DatabaseConnection.getName() method calls to DatabaseConnection.getDisplayName().

Comment 4 dynamite 2009-08-17 22:06:13 UTC
I think that I'd find this useful and so I'll implement this.
Comment 5 dynamite 2009-08-24 21:12:45 UTC
Created attachment 86587 [details]
patch file
Comment 6 dynamite 2009-08-24 21:24:02 UTC
The patch provides the user with a "Display name:" field when creating a new connection.  This field is blank by default
which will cause the JDBC connection string to display as-per current behaviour.  The name appears in the Service window
and in the connection drop-down.  The display name is persisted so that it is also used after an IDE restart.  Finally
the display name is also in the properties dialog for the connection and so can be changed.

I have tested this against MySQL and SQLServer.
Comment 7 Michel Graciano 2009-08-24 21:46:04 UTC
Hi Daniel,
thanks for your patch. :-D
I tested it against Oracle and JavaDB and works as expected.
BTW, I have two points to highlight:
MG01: Update license header for all file;

MG02: IMHO the connection combo for SQL history should be updated to reflect this change as editor combobox did.

Regards and thanks again
Comment 8 dynamite 2009-08-24 23:39:10 UTC
Hi Michel,

By licence do you mean that I put my name into the list of contributors?

I'll get the SQL History working.  Should be easy enough to do, but I may not get the patch updated until the weekend as
I'm about to be off for a few days.

Comment 9 Jiri Skrivanek 2009-08-25 11:02:26 UTC
Thank you for your patch. It works almost without problems :-) Please, see my comments below.

JS01: Display Name should be first in properties.
JS02: Existing ODBC connection shows empty display name after applying the patch (probably problem in
JS03: NewConnectionPanel:
 - rename "Name:" to "Driver Name:"
 - move "Display Name" under "Driver Name"
 - fix layout of dialog (see screen shots)
 - displayNameFieldActionPerformed not needed
 - use label from Bundle
 - add mnemonic
 - add accessible name and description
 - getDisplayName method not used
JS04: Check uniqueness of display name.
JS05: DBConnection - add javadoc
JS06: Keep NetBeans formatting (use Format - Alt+Shift+F on added code)
JS07: DatabaseConnectionConvertor - probably wrong condition "if ( !
instance.getUser().equals(instance.getDisplayName()) ) {"

Comment 10 Jiri Skrivanek 2009-08-25 11:04:13 UTC
Created attachment 86609 [details]
Wrong alignment on Windows JDK1.6 - Field Entry
Comment 11 Jiri Skrivanek 2009-08-25 11:04:40 UTC
Created attachment 86610 [details]
Wrong alignment on Windows JDK1.6 - URL Entry
Comment 12 Jiri Skrivanek 2009-09-03 13:10:31 UTC
Any progress with this?
Comment 13 dynamite 2009-09-03 23:33:49 UTC
Thanks for your comments.  I believe I now have 2 issues left.

The first is that I can't figure out how to play the display field start the start of the tabbing order in the new
connection dialog.  It is consistently placed last.  How is the tabbing order determined?

The second issue is that the display name is retrieved via classes/interfaces that are private to the Database Explorer
module, but used in the Database Core module.  I could avoid any module dependency issues by reading the display name
from the XML.  Is this the best approach?
Comment 14 Jiri Skrivanek 2009-09-04 07:54:41 UTC
Re. field position: I thought you can move it in form designer. But don't worry about it. I will fix it or ask someone
if needed.

Re. xml: I don't know what the problem is. It should be the same as user name or password.
Comment 15 dynamite 2009-09-06 23:24:25 UTC
Created attachment 87184 [details]
updated patch
Comment 16 dynamite 2009-09-06 23:41:43 UTC
I have added my updated patch.  I have been unable to resolve my tabbing issue although I did find that I had a conflict
in NewConnectionPanel.form which may not have helped.  NetBeans didn't indicate that there was a conflict in the .form
file when I was using the GUI builder.  Should I file an issue for this?

The display name is now used in the SQL history dialog.  The complication behind this is that the display name for a
connection can be set/changed subsequent to SQL statements being entered into the history - it is the url that defines
the connection rather than the name.  Such a scenario is when a user decides that they now have a growing number of
connections and decides that naming them would help.  SQLHistoryPanel works by looking up those connections that have a
defined display name and holds them in a pair of maps so that URL (as stored in SQL history) can be mapped to the
current display name.

My reason for using XMLDataObject via the look-up mechanism to get the display name was that if I stored the display
name in the SQL history then all old history statements would not use the display name.
Comment 17 Jiri Skrivanek 2009-09-08 14:03:05 UTC
Thank you for your updated patch. I applied it with couple changes. Instead of xml-based connection look-up I used
ConnectionManager.getDefault().getConnections(). I enabled Display Name property even if connection is active. After
discussion with peers I moved Display name field in connection dialog to the last place because it is optional (same as
in your first patch). If someone finds a problem with this new feature, please file a separate issue.

core-main #aeff38e79b13
Comment 18 Jiri Skrivanek 2009-09-08 14:07:45 UTC
*** Issue 151466 has been marked as a duplicate of this issue. ***
Comment 19 Jiri Kovalsky 2009-09-08 14:14:28 UTC
Great news. Thank you Jirko and Daniel!
Comment 20 Quality Engineering 2009-09-11 21:55:49 UTC
Integrated into 'main-golden', will be available in build *200909111401* on (upload may still be in progress)
User: Jiri Skrivanek <>
Log: #144112 - Enable to change display name of connection node.
Comment 21 Michel Graciano 2009-09-21 19:51:44 UTC
v. 200909210201
Comment 22 Antonin Nebuzelsky 2009-10-06 22:31:56 UTC
*** Issue 166553 has been marked as a duplicate of this issue. ***
Comment 23 Antonin Nebuzelsky 2009-10-06 22:36:54 UTC
*** Issue 162154 has been marked as a duplicate of this issue. ***
Comment 24 Antonin Nebuzelsky 2009-10-06 22:41:54 UTC
*** Issue 156154 has been marked as a duplicate of this issue. ***