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 194766 - [70cat] REGRESSION: Auto connection is not working anymore
Summary: [70cat] REGRESSION: Auto connection is not working anymore
Status: RESOLVED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: SQL Editor (show other bugs)
Version: 7.0
Hardware: All All
: P2 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: REGRESSION
: 192965 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-27 10:43 UTC by misterm
Modified: 2011-02-08 06:16 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description misterm 2011-01-27 10:43:37 UTC
Steps to reproduce:

1. Open the SQL Editor window and choose a not-connected connection;
2. Try to hit code completion

This is one of several actions that previously would automatically cause the connection to be made. Now it does nothing and worse: even after connecting, it still shows nothing. This is a very annoying regression.

Product Version = NetBeans IDE Dev (Build 110127-16b78bfb12bd)
Operating System = Windows 7 version 6.1 running on x86
Java; VM; Vendor = 1.6.0_19
Runtime = Java HotSpot(TM) Client VM 16.2-b04
Comment 1 Jiri Rechtacek 2011-01-27 12:43:49 UTC
It seems to be duplicate of issue 192965.
Comment 2 Tomas Danek 2011-02-03 14:25:45 UTC
hello, I've tried to reproduce on MacOS, as well on Windows 7, no luck:
1) created connection to Oracle DB (Thin), created second connection to JAVA DB
2) Connected to JAVA DB, disconnected Oracle DB
3) Invoked "Execute command" on Java DB node
4) Used completion in sql editor in "SELECT * from", got list of tables
5) switched in combobox disconnected Oracle DB connection
4) Used completion in sql editor in "SELECT * from" - on first completion invocation connection was established. On second invocation got list of tables.
Comment 3 misterm 2011-02-03 14:31:34 UTC
I don't use Java DB, but use JDBC-ODBC and HSQLDB as well. I can reproduce the problem for all of them. However the SQL window is already opened when I try to connect it. Try this:

1. Open a SQL Editor window for an Oracle connection (with no Java DB whatsoever);
2. Restart the IDE;
3. Go to the SQL Editor Window and choose the non-connected Oracle connection;
4. Try to hit code completion
Comment 4 Tomas Danek 2011-02-03 14:40:01 UTC
Tried now exactly those same steps and still cannot reproduce:( on first attempt i get connected, on second code completion shows relevant items. 

Product Version: NetBeans IDE Dev (Build 201102030000)
Java: 1.6.0_16; Java HotSpot(TM) Client VM 14.2-b01
System: Windows 7 version 6.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\Users\tester\.netbeans\dev
Comment 5 Michel Graciano 2011-02-03 14:49:04 UTC
Could you test it against Oracle database? I can reproduce it with Oracle easly.
Comment 6 Tomas Danek 2011-02-03 15:03:34 UTC
I was actually trying it against Oracle DB: jdbc:oracle:thin:@.....................
Comment 7 Jiri Rechtacek 2011-02-04 13:03:24 UTC
*** Bug 192965 has been marked as a duplicate of this bug. ***
Comment 8 Jiri Rechtacek 2011-02-04 13:21:43 UTC
It's weird. We (Tomas and me) cannot reproduce it with any database, Oracle including even though I believe you to be reproducible easily. Either we missed something (hidden step, special setting, what ever) or it depends somehow on your Oracle DB setup.
Is there any chance to post a webcast showing the problem? Is it really regression to NB6.9.1? Does NB6.9.1 work correctly with the same setup?
Please, use this switch -J-Dorg.netbeans.modules.db.level=FINEST to log more verbosely all DB module and reproduce it again. Exit IDE after your hit Code Completion and attach your log here. Hope it helps to figure out what's wrong. Thanks
Comment 9 Michel Graciano 2011-02-04 13:42:27 UTC
Ok, I think I know where is the problem. Try to rename your connection before hit the CC or try to run the script. :(
Sorry for incomplete bug description and thank you for your patience.
Comment 10 Michel Graciano 2011-02-04 13:44:47 UTC
(In reply to comment #8)
Yes, it is a regression because the renamed connections I had imported from 6.9.1 and there I can use them renamed or not.
Comment 11 Jiri Rechtacek 2011-02-04 15:51:01 UTC
> --- Comment #9 from Michel Graciano<hmichel@netbeans.org>   2011-02-04 13:42:27 ---
> Ok, I think I know where is the problem. Try to rename your connection before
> hit the CC or try to run the script. :(

This point makes it clear. Now I can reproduce it too. I'm investigating possible fixes....
Comment 12 Jiri Rechtacek 2011-02-07 14:11:31 UTC
fixed in core-main/rev/d5c9d9dcf205
Just a note: this changeset will not be a part of upcoming NB7.0Beta2, will be included in NB7.0 FCS.
Comment 13 Quality Engineering 2011-02-08 06:16:43 UTC
Integrated into 'main-golden', will be available in build *201102080000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/d5c9d9dcf205
User: Jiri Rechtacek <jrechtacek@netbeans.org>
Log: #194766: REGRESSION: Auto connection is not working anymore if rename DB connection node