@Deprecated public interface OrderProvider
Modifier and Type | Method and Description |
---|---|
void |
addLimit(int numberOfRows)
Deprecated.
Limit the results of this select
This is the same as calling
addLimit(int, int) with offset = 0 |
void |
addLimit(int offset,
int numberOfRows)
Deprecated.
Limit the results of this select
Note that some dialects do not support bind values at all in
LIMIT or TOP clauses! |
void |
addLimit(int offset,
Param<Integer> numberOfRows)
Deprecated.
Limit the results of this select using named parameters
Note that some dialects do not support bind values at all in
LIMIT or TOP clauses! |
void |
addLimit(Param<Integer> numberOfRows)
Deprecated.
Limit the results of this select using named parameters
Note that some dialects do not support bind values at all in
LIMIT or TOP clauses! |
void |
addLimit(Param<Integer> offset,
int numberOfRows)
Deprecated.
Limit the results of this select
Note that some dialects do not support bind values at all in
LIMIT or TOP clauses! |
void |
addLimit(Param<Integer> offset,
Param<Integer> numberOfRows)
Deprecated.
Limit the results of this select using named parameters
Note that some dialects do not support bind values at all in
LIMIT or TOP clauses! |
void |
addOrderBy(Collection<SortField<?>> fields)
Deprecated.
Adds ordering fields
|
void |
addOrderBy(Field<?>... fields)
Deprecated.
Adds ordering fields, ordering by the default sort order
|
void |
addOrderBy(int... fieldIndexes)
Deprecated.
Adds ordering fields
Indexes start at
1 in SQL! |
void |
addOrderBy(SortField<?>... fields)
Deprecated.
Adds ordering fields
|
void |
setOrderBySiblings(boolean orderBySiblings)
Deprecated.
Indicate whether the
SIBLINGS keyword should be used in an
ORDER BY clause to form an ORDER SIBLINGS BY
clause. |
@Support void addOrderBy(Field<?>... fields)
fields
- The ordering fields@Support void addOrderBy(SortField<?>... fields)
fields
- The ordering fields@Support void addOrderBy(Collection<SortField<?>> fields)
fields
- The ordering fields@Support void addOrderBy(int... fieldIndexes)
Indexes start at 1
in SQL!
Note, you can use addOrderBy(Factory.val(1).desc())
or
addOrderBy(Factory.literal(1).desc())
to apply descending
ordering
fieldIndexes
- The ordering fields@Support(value={CUBRID,ORACLE}) void setOrderBySiblings(boolean orderBySiblings)
SIBLINGS
keyword should be used in an
ORDER BY
clause to form an ORDER SIBLINGS BY
clause.
This clause can be used only along with Oracle's CONNECT BY
clause, to indicate that the hierarchical ordering should be preserved
and elements of each hierarchy should be ordered among themselves.
orderBySiblings
- @Support void addLimit(int numberOfRows)
This is the same as calling addLimit(int, int)
with offset = 0
numberOfRows
- The number of rows to return@Support(value={CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,SYBASE}) void addLimit(Param<Integer> numberOfRows)
Note that some dialects do not support bind values at all in
LIMIT
or TOP
clauses!
If there is no LIMIT
or TOP
clause in your
RDBMS, or the LIMIT
or TOP
clause does not
support bind values, this may be simulated with a
ROW_NUMBER()
window function and nested SELECT
statements.
This is the same as calling addLimit(int, int)
with offset = 0
numberOfRows
- The number of rows to return@Support(value={CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,INGRES,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,SYBASE}) void addLimit(int offset, int numberOfRows)
Note that some dialects do not support bind values at all in
LIMIT
or TOP
clauses!
If there is no LIMIT
or TOP
clause in your
RDBMS, or if your RDBMS does not natively support offsets, this is
simulated with a ROW_NUMBER()
window function and nested
SELECT
statements.
offset
- The lowest offset starting at 0numberOfRows
- The number of rows to return@Support(value={CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,SYBASE}) void addLimit(Param<Integer> offset, int numberOfRows)
Note that some dialects do not support bind values at all in
LIMIT
or TOP
clauses!
If there is no LIMIT
or TOP
clause in your
RDBMS, or the LIMIT
or TOP
clause does not
support bind values, or if your RDBMS does not natively support offsets,
this may be simulated with a ROW_NUMBER()
window function
and nested SELECT
statements.
offset
- The lowest offset starting at 0numberOfRows
- The number of rows to return@Support(value={CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,SYBASE}) void addLimit(int offset, Param<Integer> numberOfRows)
Note that some dialects do not support bind values at all in
LIMIT
or TOP
clauses!
If there is no LIMIT
or TOP
clause in your
RDBMS, or the LIMIT
or TOP
clause does not
support bind values, or if your RDBMS does not natively support offsets,
this may be simulated with a ROW_NUMBER()
window function
and nested SELECT
statements.
offset
- The lowest offset starting at 0numberOfRows
- The number of rows to return@Support(value={CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,SYBASE}) void addLimit(Param<Integer> offset, Param<Integer> numberOfRows)
Note that some dialects do not support bind values at all in
LIMIT
or TOP
clauses!
If there is no LIMIT
or TOP
clause in your
RDBMS, or the LIMIT
or TOP
clause does not
support bind values, or if your RDBMS does not natively support offsets,
this may be simulated with a ROW_NUMBER()
window function
and nested SELECT
statements.
offset
- The lowest offset starting at 0numberOfRows
- The number of rows to returnCopyright © 2013. All Rights Reserved.