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: | oracle drivers keep multiplying in the new connection dialog | ||
---|---|---|---|
Product: | db | Reporter: | ats37 <ats37> |
Component: | Code | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | CC: | romanmostyka |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 152580 | ||
Attachments: | screenshot |
Description
ats37
2008-10-31 19:34:57 UTC
Created attachment 73019 [details]
screenshot
I thought we fixed this. See issue 149492. It was fixed on Oct 9 and I see the change set in the release65 branch: http://hg.netbeans.org/release65/rev/9fde0e84ba5a So it's disconcerting that it's still there. ats37: can you get the latest build at http://bits.netbeans.org/nightly/latest and see if you can reproduce there? I'm not sure it's exactly the same problem as #149492; I'm not getting extra entries for all the drivers, only for Oracle. And of course it's only for Oracle that I've got two drivers configured, both of which have oracle.jdbc.OracleDriver set as the driver class... If I have time later this evening, though, I'll download the latest nightly and see if that does the same. I notice that the properties page for the existing Oracle connections (in NB6.5beta) don't actually display the driver name with version number that I entered, just the driver classname. Am I right in thinking it's a matter of luck (or perhaps alphabetical, or down to the order they register with the DriverManager) which jars will actually be used when I open that connection? OK, this does sound like a different bug. We'll take a look at it. Reassigned to new owner. It's still a valid issue? No response from the reporter for a long time, closed as WFM. |