public class ScrollableResultSetProcessorImpl extends Object implements ScrollableResultSetProcessor
Constructor and Description |
---|
ScrollableResultSetProcessorImpl() |
Modifier and Type | Method and Description |
---|---|
Object |
extractLogicalRowForward(ResultSet resultSet,
SessionImplementor session,
QueryParameters queryParameters)
Given a scrollable ResultSet, extract a logical row.
|
Object |
extractLogicalRowReverse(ResultSet resultSet,
SessionImplementor session,
QueryParameters queryParameters,
boolean isLogicallyAfterLast)
Like
ScrollableResultSetProcessor.extractLogicalRowForward(java.sql.ResultSet, org.hibernate.engine.spi.SessionImplementor, org.hibernate.engine.spi.QueryParameters) but here moving through the ResultSet in reverse. |
Object |
extractSingleRow(ResultSet resultSet,
SessionImplementor session,
QueryParameters queryParameters)
Give a ResultSet, extract just a single result row.
|
public Object extractSingleRow(ResultSet resultSet, SessionImplementor session, QueryParameters queryParameters)
ScrollableResultSetProcessor
Loader.loadSingleRow(ResultSet, SessionImplementor, QueryParameters, boolean)
but dropping the 'returnProxies' (that method has only one use in the entire codebase and it always passes in
false...)extractSingleRow
in interface ScrollableResultSetProcessor
resultSet
- The result set being processed.session
- The originating sessionqueryParameters
- The "parameters" used to build the querypublic Object extractLogicalRowForward(ResultSet resultSet, SessionImplementor session, QueryParameters queryParameters)
ScrollableResultSetProcessor
Loader.loadSequentialRowsForward(ResultSet, SessionImplementor, QueryParameters, boolean)
but dropping the 'returnProxies' (that method has only one use in the entire codebase and it always passes in
false...)extractLogicalRowForward
in interface ScrollableResultSetProcessor
resultSet
- The result set being processed.session
- The originating sessionqueryParameters
- The "parameters" used to build the querypublic Object extractLogicalRowReverse(ResultSet resultSet, SessionImplementor session, QueryParameters queryParameters, boolean isLogicallyAfterLast)
ScrollableResultSetProcessor
ScrollableResultSetProcessor.extractLogicalRowForward(java.sql.ResultSet, org.hibernate.engine.spi.SessionImplementor, org.hibernate.engine.spi.QueryParameters)
but here moving through the ResultSet in reverse.
Copy of Loader.loadSequentialRowsReverse(ResultSet, SessionImplementor, QueryParameters, boolean, boolean)
but dropping the 'returnProxies' (that method has only one use in the entire codebase and it always passes in
false...).
todo : is 'logicallyAfterLastRow really needed? Can't that be deduced? In fact pretty positive it is not needed.extractLogicalRowReverse
in interface ScrollableResultSetProcessor
resultSet
- The result set being processed.session
- The originating sessionqueryParameters
- The "parameters" used to build the queryisLogicallyAfterLast
- Is the result set currently positioned after the last row; again, is this really needed? How is it any diffCopyright © 2013. All rights reserved.