Package org.hibernate.dialect.pagination
Class Oracle12LimitHandler
java.lang.Object
org.hibernate.dialect.pagination.AbstractLimitHandler
org.hibernate.dialect.pagination.Oracle12LimitHandler
- All Implemented Interfaces:
LimitHandler
A
LimitHandler
for databases which support the
ANSI SQL standard syntax FETCH FIRST m ROWS ONLY
and OFFSET n ROWS FETCH NEXT m ROWS ONLY
.-
Field Summary
FieldsFields inherited from class org.hibernate.dialect.pagination.AbstractLimitHandler
NO_LIMIT
-
Method Summary
Modifier and TypeMethodDescriptionboolean
Usually, the offset comes before the limit, but occasionally the offset is specified after the limit.protected String
processSql
(String sql, boolean hasFirstRow, boolean hasMaxRows, LockOptions lockOptions) protected String
processSql
(String sql, int forUpdateIndex, boolean hasFirstRow, boolean hasMaxRows) processSql
(String sql, Limit limit, QueryOptions queryOptions) protected String
processSqlOffsetFetch
(String sql, boolean hasFirstRow, boolean hasMaxRows) final boolean
Does this handler support limiting query results?boolean
Does this handler support offsetting query results without also specifying a limit?boolean
Does the limit clause expect the number of the last row, or the "page size", the maximum number of rows we want to receive? Hibernate'sQuery.setMaxResults(int)
accepts the page size, so the number of the last row is obtained by adding the number of the first row, which is one greater thanQuery.setFirstResult(int)
.Methods inherited from class org.hibernate.dialect.pagination.AbstractLimitHandler
bindLimitParameters, bindLimitParametersAtEndOfQuery, bindLimitParametersAtStartOfQuery, bindLimitParametersFirst, convertToFirstRowValue, forceLimitUsage, getFirstRow, getForUpdatePattern, getMaxOrLimit, hasFirstRow, hasMaxRows, insertAfterDistinct, insertAfterSelect, insertAtEnd, insertBeforeForUpdate, processSql, setMaxRows, supportsLimitOffset, supportsVariableLimit
-
Field Details
-
INSTANCE
-
-
Method Details
-
processSql
-
processSql
protected String processSql(String sql, boolean hasFirstRow, boolean hasMaxRows, LockOptions lockOptions) -
processSqlOffsetFetch
-
processSql
-
supportsLimit
public final boolean supportsLimit()Description copied from interface:LimitHandler
Does this handler support limiting query results?- Specified by:
supportsLimit
in interfaceLimitHandler
- Overrides:
supportsLimit
in classAbstractLimitHandler
- Returns:
- True if this handler supports limit alone.
-
supportsOffset
public boolean supportsOffset()Description copied from interface:LimitHandler
Does this handler support offsetting query results without also specifying a limit?- Specified by:
supportsOffset
in interfaceLimitHandler
- Overrides:
supportsOffset
in classAbstractLimitHandler
- Returns:
- True if this handler supports offset alone.
-
bindLimitParametersInReverseOrder
public boolean bindLimitParametersInReverseOrder()Description copied from class:AbstractLimitHandler
Usually, the offset comes before the limit, but occasionally the offset is specified after the limit. Does this dialect require us to bind the parameters in reverse order?- Overrides:
bindLimitParametersInReverseOrder
in classAbstractLimitHandler
- Returns:
- true if the correct order is limit then offset
-
useMaxForLimit
public boolean useMaxForLimit()Description copied from class:AbstractLimitHandler
Does the limit clause expect the number of the last row, or the "page size", the maximum number of rows we want to receive? Hibernate'sQuery.setMaxResults(int)
accepts the page size, so the number of the last row is obtained by adding the number of the first row, which is one greater thanQuery.setFirstResult(int)
.- Overrides:
useMaxForLimit
in classAbstractLimitHandler
- Returns:
- true if the limit clause expects the number of the last row, false if it expects the page size
-