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 184700 - [69cat] com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Result set is positioned after last row.
Summary: [69cat] com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: ...
Status: RESOLVED DUPLICATE of bug 184846
Alias: None
Product: db
Classification: Unclassified
Component: Show Data (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-22 09:18 UTC by kawazu428
Modified: 2010-04-23 14:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 168364

Attachments
stacktrace (1.08 KB, text/plain)
2010-04-22 09:18 UTC, kawazu428 		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 kawazu428 2010-04-22 09:18:46 UTC 
Build: NetBeans IDE Dev (Build 201004220200)
VM: Java HotSpot(TM) Client VM, 16.2-b04, Java(TM) SE Runtime Environment, 1.6.0_19-b04
OS: Linux

Stacktrace: 
com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Result set is positioned after last row.
   at com.sap.dbtech.jdbc.ResultSetSapDB.getCurrentRecord(ResultSetSapDB.java:2740)
   at com.sap.dbtech.jdbc.ResultSetSapDB.getString(ResultSetSapDB.java:1248)
   at org.netbeans.modules.db.dataview.util.DBReadWriteHelper.readResultSet(DBReadWriteHelper.java:192)
   at org.netbeans.modules.db.dataview.output.SQLExecutionHelper.loadDataFrom(SQLExecutionHelper.java:509)
   at org.netbeans.modules.db.dataview.output.SQLExecutionHelper.initialDataLoad(SQLExecutionHelper.java:131)
   at org.netbeans.modules.db.dataview.output.DataView.create(DataView.java:102)
Comment 1 kawazu428 2010-04-22 09:18:51 UTC 
Created attachment 97841 [details]
stacktrace
Comment 2 Jiri Rechtacek 2010-04-23 14:45:48 UTC 

*** This bug has been marked as a duplicate of bug 184846 ***