public interface DivideByOnStep
XYZ*Step
types directly from client code
It is usually not recommended to reference any XYZ*Step
types
directly from client code, or assign them to local variables. When writing
dynamic SQL, creating a statement's components dynamically, and passing them
to the DSL API statically is usually a better choice. See the manual's
section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql.
Drawbacks of referencing the XYZ*Step
types directly:
Modifier and Type | Method and Description |
---|---|
DivideByOnConditionStep |
on(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
on(Condition) or
on(Field) instead. Due to ambiguity between calling
this method using Field.equals(Object) argument, vs.
calling the other method via a Field.equal(Object)
argument, this method will be removed in the future. |
DivideByOnConditionStep |
on(Condition... conditions)
Add a division condition to the
DIVIDE BY clause, connecting
them with each other with Operator.AND . |
DivideByOnConditionStep |
on(Condition condition)
Add a division condition to the
DIVIDE BY clause, connecting
them with each other with Operator.AND . |
DivideByOnConditionStep |
on(Field<Boolean> condition)
Add a division condition to the
DIVIDE BY clause |
DivideByOnConditionStep |
on(SQL sql)
Add a division condition to the
DIVIDE BY clause
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DivideByOnConditionStep |
on(String sql)
Add a division condition to the
DIVIDE BY clause
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DivideByOnConditionStep |
on(String sql,
Object... bindings)
Add a division condition to the
DIVIDE BY clause
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DivideByOnConditionStep |
on(String sql,
QueryPart... parts)
Add a division condition to the
DIVIDE BY clause
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
@Support DivideByOnConditionStep on(Condition condition)
DIVIDE BY
clause, connecting
them with each other with Operator.AND
.@Support DivideByOnConditionStep on(Condition... conditions)
DIVIDE BY
clause, connecting
them with each other with Operator.AND
.@Support DivideByOnConditionStep on(Field<Boolean> condition)
DIVIDE BY
clause@Deprecated @Support DivideByOnConditionStep on(Boolean condition)
on(Condition)
or
on(Field)
instead. Due to ambiguity between calling
this method using Field.equals(Object)
argument, vs.
calling the other method via a Field.equal(Object)
argument, this method will be removed in the future.DIVIDE BY
clause@Support @PlainSQL DivideByOnConditionStep on(SQL sql)
DIVIDE BY
clause
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
DSL.condition(SQL)
,
SQL
@Support @PlainSQL DivideByOnConditionStep on(String sql)
DIVIDE BY
clause
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
DSL.condition(String)
,
SQL
@Support @PlainSQL DivideByOnConditionStep on(String sql, Object... bindings)
DIVIDE BY
clause
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
@Support @PlainSQL DivideByOnConditionStep on(String sql, QueryPart... parts)
DIVIDE BY
clause
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Copyright © 2019. All rights reserved.