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 170090 - java.sql.SQLException: no database metadata available
Summary: java.sql.SQLException: no database metadata available
Status: RESOLVED INCOMPLETE
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Rechtacek
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-09 09:36 UTC by saeed_z_f
Modified: 2009-09-03 10:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 155310

Attachments
stacktrace (619 bytes, text/plain)
2009-08-09 09:36 UTC, saeed_z_f 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description saeed_z_f 2009-08-09 09:36:13 UTC 
Build: NetBeans IDE 6.7.1 (Build 200907230233)
VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Windows XP, 5.1, x86

User Comments:
saeed_Z_F: When I create Entity class from a SQL Server database.



Stacktrace: 
java.sql.SQLException: no database metadata available
        at org.netbeans.lib.ddl.adaptors.DefaultAdaptor.isReadOnly(DefaultAdaptor.java:435)
        at org.netbeans.modules.db.explorer.node.ConnectionNode.updateLocalProperties(ConnectionNode.java:165)
        at org.netbeans.modules.db.explorer.node.ConnectionNode.access$200(ConnectionNode.java:71)
        at org.netbeans.modules.db.explorer.node.ConnectionNode$2.run(ConnectionNode.java:300)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:577)
        at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1030)
Comment 1 saeed_z_f 2009-08-09 09:36:21 UTC 
Created attachment 86004 [details]
stacktrace
Comment 2 Jiri Rechtacek 2009-09-03 10:51:47 UTC 
I'm sorry I'm not able to evaluate this problem so far. I need some more information. Could you note which driver (a jar
library) are you using? Can you describe the steps how to reproduce the problem from scratch? Thanks