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 108460 - Suggest that the user may need to upgrade their driver if there is an error with metadata
Summary: Suggest that the user may need to upgrade their driver if there is an error w...
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: John Baker
Depends on:
Reported: 2007-06-28 19:32 UTC by David Vancouvering
Modified: 2008-02-06 14:39 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description David Vancouvering 2007-06-28 19:32:15 UTC
A lot of users get confused when they attempt to bind a table or query to a visual component, and it doesn't work. In
particular, they don't understand why it works for them to view the table or query outside of NB.  This is usually
because metadata doesn't work, and this is often because the database driver is old or otherwise not supported.

We should detect if the version of the driver is a supported version, and if it isn't, suggest that the user upgrade
their driver to a supported one.

This doesn't mean we should automatically fail if the driver's not supported, but only if there *is* an error, include
the suggestion to upgrade in the error message.

If it is too much work to keep a list of supported drivers and detect this at runtime, we should at least suggest an
upgrade as a potential solution.  

This is a very common question on the list, so I'm rating this a p2.
Comment 1 _ jimdavidson 2007-06-28 22:09:20 UTC
See my reply to #105684 (BTW, how does one do "See Also" in IssueZilla)?

I think checking specific driver versions is a bad idea, for a lot of reasons.  We can check the major version, either
when the user adds the driver in the DB Explorer or when he creates a connection with it.

Otherwise, best is to catch and report the various failures that occur.

Leaving this as a Defect for now, but it may eventually be changed to an Enhancement, for consistency with #105864.
Comment 2 _ jimdavidson 2007-06-28 22:20:15 UTC
This and #105864 should be handled by the same person, since the same solution should take care of both. (Checking
JDBCMajorVersion in one or more places.)

David, since you're taking #105864, I've assigned this one to you as well.  Feel free to assign them both to me.
Comment 3 Jayashri Visvanathan 2007-07-26 21:34:18 UTC
David, are you planning to fix this for Beta 1. If not it should be downgraded or marked as an enhancement
so that it won't affect the quality criteria.
Comment 4 David Vancouvering 2007-07-31 17:43:12 UTC
A discussion in our i-team, we agreed this would be nice, but is not a P2
Comment 5 John Baker 2007-10-29 19:32:18 UTC
driver compatibility won't apply globally in NetBeans.  For example, desktop applications that use Oracle the Oracle
driver version 9 may be compatible.  However, for Visual JSF applications require version 10.1

At least the driver versions should be mentioned in the Release notes.  I had suggested the Release Notes point to the
wiki page of supported Drivers.  I'll check on this
Comment 6 John Baker 2007-11-02 01:16:37 UTC
Won't fix for 6.0