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.
| Modifier and Type | Field and Description |
|---|---|
| public static LimitOffsetLimitHandler | |
| public static LimitOffsetLimitHandler |
| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| public final boolean | bindLimitParametersInReverseOrder()
Overrides org. |
| protected String | limitClause(boolean hasFirstRow)
Implements abstract org. |
| protected String | |
| public boolean | supportsOffset()
Overrides org. Implements org. |
| INSTANCE | back to summary |
|---|---|
| public static LimitOffsetLimitHandler INSTANCE | |
| OFFSET_ONLY_INSTANCE | back to summary |
|---|---|
| public static LimitOffsetLimitHandler OFFSET_ONLY_INSTANCE | |
| LimitOffsetLimitHandler | back to summary |
|---|---|
| public LimitOffsetLimitHandler() | |
| bindLimitParametersInReverseOrder | back to summary |
|---|---|
| public final boolean bindLimitParametersInReverseOrder() Overrides org. Doc from org. 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?
| |
| limitClause | back to summary |
|---|---|
| protected String limitClause(boolean hasFirstRow) Implements abstract org.
| |
| offsetOnlyClause | back to summary |
|---|---|
| protected String offsetOnlyClause() Overrides org.
| |
| supportsOffset | back to summary |
|---|---|
| public boolean supportsOffset() Overrides org. Implements org. Doc from org. Does this handler support offsetting query results without also specifying a limit?
| |