Class LimitOffsetLimitHandler

java.lang.Object

org.hibernate.dialect.pagination.spi.AbstractLimitHandler

org.hibernate.dialect.pagination.spi.AbstractSimpleLimitHandler

org.hibernate.dialect.pagination.spi.LimitOffsetLimitHandler

All Implemented Interfaces:

LimitHandler

@SPI({USE,IMPLEMENT})
public class LimitOffsetLimitHandler
extends AbstractSimpleLimitHandler

A LimitHandler for databases like PostgreSQL, H2, and HSQL that support the syntax LIMIT n OFFSET m. Note that this syntax does not allow specification of an offset without a limit.

Since:

8.0

Field Summary

Fields

Modifier and Type	Field	Description
static LimitOffsetLimitHandler	INSTANCE
static LimitOffsetLimitHandler	OFFSET_ONLY_INSTANCE

Fields inherited from class AbstractLimitHandler

NO_LIMIT

Constructor Summary

Constructors

Constructor	Description
LimitOffsetLimitHandler()

Method Summary

Modifier and Type	Method	Description
final boolean	bindLimitParametersInReverseOrder()	Usually, the offset comes before the limit, but occasionally the offset is specified after the limit.
protected String	limitClause(boolean hasFirstRow, PaginationRequest request)
protected String	offsetOnlyClause(PaginationRequest request)
boolean	supportsOffset()	Does this handler support offsetting query results without also specifying a limit?

Methods inherited from class AbstractSimpleLimitHandler

insert, processSql, supportsLimit, supportsVariableLimit

Methods inherited from class AbstractLimitHandler

bindLimitParametersFirst, bindLimitParameterValues, convertToFirstRowValue, forceLimitUsage, getFirstRow, getForUpdatePattern, getMaxOrLimit, hasFirstRow, hasMaxRows, insertAfterDistinct, insertAfterSelect, insertAtEnd, insertBeforeForUpdate, jdbcInstructions, jdbcMaxRows, parameterPositionStart, result, rowsToSkip, supportsLimitOffset, useMaxForLimit

Methods inherited from class Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Details

INSTANCE

public static LimitOffsetLimitHandler INSTANCE

OFFSET_ONLY_INSTANCE

public static LimitOffsetLimitHandler OFFSET_ONLY_INSTANCE

Constructor Details

LimitOffsetLimitHandler

@SPI({USE,IMPLEMENT})
public LimitOffsetLimitHandler()

Method Details

limitClause

protected String limitClause(boolean hasFirstRow,
 PaginationRequest request)

Specified by:

limitClause in class AbstractSimpleLimitHandler

offsetOnlyClause

protected String offsetOnlyClause(PaginationRequest request)

Overrides:

offsetOnlyClause in class AbstractSimpleLimitHandler

bindLimitParametersInReverseOrder

public final 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 class AbstractLimitHandler

Returns:

true if the correct order is limit then offset

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 interface LimitHandler

Overrides:

supportsOffset in class AbstractSimpleLimitHandler

Returns:

True if this handler supports offset alone.