Top Description Methods
org.hibernate.loader.plan.exec.process.spi

public Interface ScrollableResultSetProcessor

Imports
java.sql.ResultSet, org.hibernate.engine.spi.QueryParameters, .SessionImplementor, .SharedSessionContractImplementor
Contract for processing JDBC ResultSets a single logical row at a time. These are intended for use by org.hibernate.ScrollableResults implementations. NOTE : these methods initially taken directly from org.hibernate.loader.Loader counterparts in an effort to break Loader into manageable pieces, especially in regards to the processing of result sets.
Author
Steve Ebersole

Method Summary

Modifier and TypeMethod and Description
public Object

Returns:

The extracted result row
extractLogicalRowForward(final ResultSet
The result set being processed.
resultSet, final SessionImplementor
The originating session
session, final QueryParameters
The "parameters" used to build the query
queryParameters)

Deprecated as a consequence of SessionImplementor being deprecated.
Given a scrollable ResultSet, extract a logical row.
public Object

Returns:

The extracted result row
extractLogicalRowReverse(ResultSet
The result set being processed.
resultSet, SessionImplementor
The originating session
session, QueryParameters
The "parameters" used to build the query
queryParameters, boolean
Is the result set currently positioned after the last row; again, is this really needed? How is it any diff
isLogicallyAfterLast)

Deprecated as a consequence of SessionImplementor being deprecated.
Like extractLogicalRowForward but here moving through the ResultSet in reverse.
public Object

Returns:

The extracted result row
extractSingleRow(ResultSet
The result set being processed.
resultSet, SessionImplementor
The originating session
session, QueryParameters
The "parameters" used to build the query
queryParameters)

Deprecated as a consequence of SessionImplementor being deprecated.
Give a ResultSet, extract just a single result row.

Method Detail

extractLogicalRowForwardback to summary
public Object extractLogicalRowForward(final ResultSet resultSet, final SessionImplementor session, final QueryParameters queryParameters)

Deprecated

as a consequence of SessionImplementor being deprecated. See corresponding docs for further information.

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 org.hibernate.loader.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...)

Parameters
resultSet:ResultSet

The result set being processed.

session:SessionImplementor

The originating session

queryParameters:QueryParameters

The "parameters" used to build the query

Returns:Object

The extracted result row

Exceptions
HibernateException:
Indicates a problem extracting values from the result set.
extractLogicalRowReverseback to summary
public Object extractLogicalRowReverse(ResultSet resultSet, SessionImplementor session, QueryParameters queryParameters, boolean isLogicallyAfterLast)

Deprecated

as a consequence of SessionImplementor being deprecated. See corresponding docs for further information.

Like extractLogicalRowForward but here moving through the ResultSet in reverse. Copy of org.hibernate.loader.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.

Parameters
resultSet:ResultSet

The result set being processed.

session:SessionImplementor

The originating session

queryParameters:QueryParameters

The "parameters" used to build the query

isLogicallyAfterLast:boolean

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

Returns:Object

The extracted result row

Exceptions
HibernateException:
Indicates a problem extracting values from the result set.
extractSingleRowback to summary
public Object extractSingleRow(ResultSet resultSet, SessionImplementor session, QueryParameters queryParameters)

Deprecated

as a consequence of SessionImplementor being deprecated. See corresponding docs for further information.

Give a ResultSet, extract just a single result row. Copy of org.hibernate.loader.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...)

Parameters
resultSet:ResultSet

The result set being processed.

session:SessionImplementor

The originating session

queryParameters:QueryParameters

The "parameters" used to build the query

Returns:Object

The extracted result row

Exceptions
HibernateException:
Indicates a problem extracting values from the result set.