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: | Suggest that the user may need to upgrade their driver if there is an error with metadata | ||
---|---|---|---|
Product: | obsolete | Reporter: | David Vancouvering <davidvc> |
Component: | visualweb | Assignee: | John Baker <jbaker> |
Status: | NEW --- | ||
Severity: | blocker | CC: | romanmostyka |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
David Vancouvering
2007-06-28 19:32:15 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. 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. 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. A discussion in our i-team, we agreed this would be nice, but is not a P2 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 Won't fix for 6.0 |