public interface ScrollableResultSetProcessor
ScrollableResults
implementations.
NOTE : these methods initially taken directly from Loader
counterparts in an effort
to break Loader into manageable pieces, especially in regards to the processing of result sets.Modifier and Type | Method and Description |
---|---|
java.lang.Object |
extractLogicalRowForward(java.sql.ResultSet resultSet,
SessionImplementor session,
QueryParameters queryParameters)
Given a scrollable ResultSet, extract a logical row.
|
java.lang.Object |
extractLogicalRowReverse(java.sql.ResultSet resultSet,
SessionImplementor session,
QueryParameters queryParameters,
boolean isLogicallyAfterLast)
Like
extractLogicalRowForward(java.sql.ResultSet, org.hibernate.engine.spi.SessionImplementor, org.hibernate.engine.spi.QueryParameters) but here moving through the ResultSet in reverse. |
java.lang.Object |
extractSingleRow(java.sql.ResultSet resultSet,
SessionImplementor session,
QueryParameters queryParameters)
Give a ResultSet, extract just a single result row.
|
java.lang.Object extractSingleRow(java.sql.ResultSet resultSet, SessionImplementor session, QueryParameters queryParameters)
org.hibernate.loader.Loader#loadSingleRow(java.sql.ResultSet, org.hibernate.engine.spi.SessionImplementor, org.hibernate.engine.spi.QueryParameters, boolean)
but dropping the 'returnProxies' (that method has only one use in the entire codebase and it always passes in
false...)resultSet
- The result set being processed.session
- The originating sessionqueryParameters
- The "parameters" used to build the queryHibernateException
- Indicates a problem extracting values from the result set.java.lang.Object extractLogicalRowForward(java.sql.ResultSet resultSet, SessionImplementor session, QueryParameters queryParameters)
org.hibernate.loader.Loader#loadSequentialRowsForward(java.sql.ResultSet, org.hibernate.engine.spi.SessionImplementor, org.hibernate.engine.spi.QueryParameters, boolean)
but dropping the 'returnProxies' (that method has only one use in the entire codebase and it always passes in
false...)resultSet
- The result set being processed.session
- The originating sessionqueryParameters
- The "parameters" used to build the queryHibernateException
- Indicates a problem extracting values from the result set.java.lang.Object extractLogicalRowReverse(java.sql.ResultSet resultSet, SessionImplementor session, QueryParameters queryParameters, boolean isLogicallyAfterLast)
extractLogicalRowForward(java.sql.ResultSet, org.hibernate.engine.spi.SessionImplementor, org.hibernate.engine.spi.QueryParameters)
but here moving through the ResultSet in reverse.
Copy of org.hibernate.loader.Loader#loadSequentialRowsReverse(java.sql.ResultSet, org.hibernate.engine.spi.SessionImplementor, org.hibernate.engine.spi.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.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 diffHibernateException
- Indicates a problem extracting values from the result set.Copyright © 2001-2018 Red Hat, Inc. All Rights Reserved.