- All Superinterfaces:
Attachable
,AttachableQueryPart
,AutoCloseable
,DMLQuery<R>
,Flow.Publisher<Integer>
,Publisher<Integer>
,org.reactivestreams.Publisher<Integer>
,Query
,QueryPart
,RowCountQuery
,Serializable
,Statement
,Update<R>
,UpdateFinalStep<R>
,UpdateLimitStep<R>
,UpdateOrderByStep<R>
,UpdateReturningStep<R>
Update
's DSL API.
Example:
DSLContext create = DSL.using(configuration);
create.update(table)
.set(field1, value1)
.set(field2, value2)
.where(field1.greaterThan(100))
.execute();
Referencing 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:
- They're operating on mutable implementations (as of jOOQ 3.x)
- They're less composable and not easy to get right when dynamic SQL gets complex
- They're less readable
- They might have binary incompatible changes between minor releases
- Author:
- Lukas Eder
-
Method Summary
Modifier and TypeMethodDescription@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.AND
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.AND
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.AND
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.AND
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.AND
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.AND
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with an EXISTS clause using theOperator.AND
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with a negated other one using theOperator.AND
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with a negated other one using theOperator.AND
operator@NotNull UpdateConditionStep<R>
andNotExists
(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.AND
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.OR
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.OR
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.OR
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.OR
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.OR
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with another one using theOperator.OR
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with an EXISTS clause using theOperator.OR
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator@NotNull UpdateConditionStep<R>
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator@NotNull UpdateConditionStep<R>
orNotExists
(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.OR
operatorMethods inherited from interface org.jooq.Attachable
attach, configuration, detach
Methods inherited from interface org.jooq.AttachableQueryPart
getBindValues, getParam, getParams, getSQL, getSQL
Methods inherited from interface org.reactivestreams.Publisher
subscribe
Methods inherited from interface org.jooq.Query
bind, bind, cancel, close, execute, executeAsync, executeAsync, isExecutable, keepStatement, poolable, queryTimeout
Methods inherited from interface org.jooq.QueryPart
$replace, $replace, $traverse, $traverse, equals, hashCode, toString
Methods inherited from interface org.jooq.UpdateLimitStep
limit, limit
Methods inherited from interface org.jooq.UpdateOrderByStep
orderBy, orderBy, orderBy
Methods inherited from interface org.jooq.UpdateReturningStep
returning, returning, returning, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult
-
Method Details
-
and
Combine the currently assembled conditions with another one using theOperator.AND
operator -
and
Combine the currently assembled conditions with another one using theOperator.AND
operator -
and
Combine the currently assembled conditions with another one using theOperator.AND
operatorNOTE: 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!
- See Also:
-
and
Combine the currently assembled conditions with another one using theOperator.AND
operatorNOTE: 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!
- See Also:
-
and
@NotNull @CheckReturnValue @Support @PlainSQL @NotNull UpdateConditionStep<R> and(String sql, Object... bindings) Combine the currently assembled conditions with another one using theOperator.AND
operatorNOTE: 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!
-
and
@NotNull @CheckReturnValue @Support @PlainSQL @NotNull UpdateConditionStep<R> and(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using theOperator.AND
operatorNOTE: 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!
-
andNot
Combine the currently assembled conditions with a negated other one using theOperator.AND
operator -
andNot
@NotNull @CheckReturnValue @Support @NotNull UpdateConditionStep<R> andNot(Field<Boolean> condition) Combine the currently assembled conditions with a negated other one using theOperator.AND
operator -
andExists
Combine the currently assembled conditions with an EXISTS clause using theOperator.AND
operator -
andNotExists
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.AND
operator -
or
Combine the currently assembled conditions with another one using theOperator.OR
operator -
or
Combine the currently assembled conditions with another one using theOperator.OR
operator -
or
Combine the currently assembled conditions with another one using theOperator.OR
operatorNOTE: 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!
- See Also:
-
or
Combine the currently assembled conditions with another one using theOperator.OR
operatorNOTE: 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!
- See Also:
-
or
@NotNull @CheckReturnValue @Support @PlainSQL @NotNull UpdateConditionStep<R> or(String sql, Object... bindings) Combine the currently assembled conditions with another one using theOperator.OR
operatorNOTE: 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!
-
or
@NotNull @CheckReturnValue @Support @PlainSQL @NotNull UpdateConditionStep<R> or(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using theOperator.OR
operatorNOTE: 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!
-
orNot
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator -
orNot
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator -
orExists
Combine the currently assembled conditions with an EXISTS clause using theOperator.OR
operator -
orNotExists
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.OR
operator
-