-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution:
Won't Fix
-
Affects Version/s: EAP_EWP 5.1.0, 4.3.0.GA_CP09, 4.2.0.GA_CP10
-
Fix Version/s: TBD
-
Component/s: Hibernate
-
Labels:None
-
Affects:Release Notes
-
Release Notes Text:
-
Release Notes Docs Status:Not Required
To determine if a ResultSet is empty, FetchingScrollableResultsImpl.isResultSetEmpty() returns:
currentPosition == 0 && ! getResultSet().isBeforeFirst() && ! getResultSet().isAfterLast();
For Sybase ASE 15, when the ResultSet is empty, FetchingScrollableResultsImpl.isResultSetEmpty() returns false.
The problem is that Sybase JDBC returns true for ResultSet.isBeforeFirst() and/or ResultSet.isAfterLast() when the ResultSet is empty.
An empty ResultSet is properly detected for Oracle 10g, SQL Server, MySQL, and DB2 9.7.
This looks like a bug in Sybase JDBC.
- is related to
-
JBPAPP-4095 HHH-5096 FetchingScrollableResultsImpl.last() does not move to the last result if cursor is after the last result
-
- Closed
-