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: | SQLServer 2005/Netbeans 5.5 Issue : Custom schemas not visible under database while creating EJB 3.0 Entity Classes from database | ||
---|---|---|---|
Product: | db | Reporter: | chenji <chenji> |
Component: | Code | Assignee: | Andrei Badea <abadea> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
SQL File
Problem Pictures |
Description
chenji
2007-09-13 09:51:22 UTC
Created attachment 48723 [details]
SQL File
Created attachment 48724 [details]
Problem Pictures
Issues occurs on both NetBeans 5.5 & 5.5.1 versions. Tried connecting using Microsoft SQL Server 2005 JDBC Driver 1.1 & 1.2 versions(sqljdbc.jar) but still the problems exists. Does not display any customer schemas in the select schema : drop down list under Advanced Tab while creating the Entity classes...... This is not an issue in NetBeans. The MS SQL Server 2005 JDBC drivers (sqljdbc.jar) do not return the schemas from DatabaseMetaData.getSchemas(). Instead, they return the database users. I checked with another Java database tool and it gives the same result as NetBeans. I can't think of a workaround other than using database users instead of schemas for separation, although I understand that may be impractical or perhaps even impossible, depending on the customer's security requirements. I also checked the jTDS driver, but it doesn't return the schemas either. Downgrading to P3, since this is not an issue in NetBeans. Will probably close as INVALID soon. Closing according to desc5. Should we release-note this? It sounds like the bug is in the database, not the driver, since jTDS doesn't work either. Either way, it's a use case that doesn't work in NetBeans, so we should warn the user. The best case would be to present some sort of warning when the user tries to connect. But, I'm not sure there's an obvious place to do this, without being intrusive. When the driver is added? When the connection is created? When the user connects? A release note is a fallback, and I think that's adequate in this case. It's not a bug in the database, it's in the driver. Both drivers -- they do the same thing. Actually I'm not sure it can be even considered a bug. MS SQL 2005 has both users and schemas, and JDBC has only schemas. The drivers authors had to choose which of those entities to support in JDBC (and it's good they made the same choice). I don't see much point in putting this in the release notes. Generally, you only want to put very important issues in the release notes -- those that many users are likely to run into. A bug in a driver which has only been reported once in the two years or so I'm working the databases does not IMHO qualify. |