程序包 org.hibernate.loader.plan.exec.process.spi

接口 ScrollableResultSetProcessor

public interface ScrollableResultSetProcessor

Contract for processing JDBC ResultSets a single logical row at a time. These are intended for use by 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.

作者:

Steve Ebersole

方法概要

修饰符和类型	方法	说明
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 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.

方法详细资料

extractSingleRow

Object extractSingleRow(ResultSet resultSet,
                        SessionImplementor session,
                        QueryParameters queryParameters)

Give a ResultSet, extract just a single result row. Copy of Loader.loadSingleRow(ResultSet, SharedSessionContractImplementor, 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 session

queryParameters - The "parameters" used to build the query

返回:

The extracted result row

抛出:

HibernateException - Indicates a problem extracting values from the result set.

extractLogicalRowForward

Object extractLogicalRowForward(ResultSet resultSet,
                                SessionImplementor session,
                                QueryParameters queryParameters)

Given a scrollable ResultSet, extract a logical row. The assumption here is that the ResultSet is already properly ordered to account for any to-many fetches. Multiple ResultSet rows are read into a single query result "row". Copy of Loader.loadSequentialRowsForward(ResultSet, SharedSessionContractImplementor, 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 session

queryParameters - The "parameters" used to build the query

返回:

The extracted result row

抛出:

HibernateException - Indicates a problem extracting values from the result set.

extractLogicalRowReverse

Object extractLogicalRowReverse(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. Copy of Loader.loadSequentialRowsReverse(ResultSet, SharedSessionContractImplementor, 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 session

queryParameters - The "parameters" used to build the query

isLogicallyAfterLast - Is the result set currently positioned after the last row; again, is this really needed? How is it any diff

返回:

The extracted result row

抛出:

HibernateException - Indicates a problem extracting values from the result set.