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 255037 - java.sql.SQLException: [DataDirect][OpenEdge JDBC Driver][OpenEdge] Inconsistent types (7481)
Summary: java.sql.SQLException: [DataDirect][OpenEdge JDBC Driver][OpenEdge] Inconsist...
Status: RESOLVED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Show Data (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: matthias42
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-07 01:42 UTC by brettryan
Modified: 2015-09-10 01:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 219739


Attachments
stacktrace (1.38 KB, text/plain)
2015-09-07 01:42 UTC, brettryan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description brettryan 2015-09-07 01:42:54 UTC
Build: NetBeans IDE Dev (Build 201508230002)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.45-b02, Java(TM) SE Runtime Environment, 1.8.0_45-b14
OS: Mac OS X

User Comments:
brettryan: Am assuming a JDBC driver problem, though this shouldn't produce a reportable exception and instead the exception should be reported to the output window.

Actual query was select range_id.NEXTVAL from jrg_mstr




Stacktrace: 
java.sql.SQLException: [DataDirect][OpenEdge JDBC Driver][OpenEdge] Inconsistent types (7481)
   at com.ddtek.jdbc.openedge.client.OpenEdgeClientRequest.fetchProcessReply(OpenEdgeClientRequest.java:0)
   at com.ddtek.jdbc.openedge.client.OpenEdgeClientRequest.fetch(OpenEdgeClientRequest.java:0)
   at com.ddtek.jdbc.openedge.OpenEdgeImplResultSet.fetchAtPosition(OpenEdgeImplResultSet.java:0)
   at com.ddtek.jdbc.base.BaseImplResultSet.next(BaseImplResultSet.java:0)
   at com.ddtek.jdbc.base.BaseResultSet.next(BaseResultSet.java:0)
   at org.netbeans.modules.db.dataview.output.SQLExecutionHelper.setTotalCount(SQLExecutionHelper.java:963)
Comment 1 brettryan 2015-09-07 01:42:56 UTC
Created attachment 155930 [details]
stacktrace
Comment 2 matthias42 2015-09-08 20:27:00 UTC
I agree that reporting this as an exception on severe level is not appropriate. But I also will not report this in the output window. The JDBC driver is broken - sofar so bad, so we extract the information that can be extract and be done with it - the total number of result will be unknown.

This changeset:

http://hg.netbeans.org/core-main/rev/397137d72572

changes the behaviour of the method as described. The exception is logged to the netbeans log, no message is shown to the user, the total number of rows is reported as "N/A".

In the next few days a nightly build with this change will be build. Please verify that this fixes the issue. Thank you!
Comment 3 Quality Engineering 2015-09-10 01:28:51 UTC
Integrated into 'main-silver', will be available in build *201509100002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/397137d72572
User: Matthias Blaesing <matthias42@netbeans.org>
Log: #255037: Report exception when fetching count result set on INFO instead of SEVERE level