-
- All Superinterfaces:
Attachable
,AutoCloseable
,Flow.Publisher<Integer>
,org.reactivestreams.Publisher<Integer>
,Query
,QueryPart
,RowCountQuery
,Serializable
,Statement
,Update<R>
,UpdateFinalStep<R>
,UpdateLimitStep<R>
,UpdateOrderByStep<R>
,UpdateReturningStep<R>
- All Known Subinterfaces:
UpdateFromStep<R>
,UpdateSetMoreStep<R>
public interface UpdateWhereStep<R extends Record> extends UpdateOrderByStep<R>
This type is used for theUpdate
'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 codeIt 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
All Methods Instance Methods Abstract Methods Deprecated Methods Modifier and Type Method Description UpdateConditionStep<R>
where(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Usewhere(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orwhere(Field)
instead.UpdateConditionStep<R>
where(String sql)
Add conditions to the queryUpdateConditionStep<R>
where(String sql, Object... bindings)
Add conditions to the queryUpdateConditionStep<R>
where(String sql, QueryPart... parts)
Add conditions to the queryUpdateConditionStep<R>
where(Collection<? extends Condition> conditions)
Add conditions to the query, connecting them with each other withOperator.AND
.UpdateConditionStep<R>
where(Condition condition)
Add conditions to the query, connecting them with each other withOperator.AND
.UpdateConditionStep<R>
where(Condition... conditions)
Add conditions to the query, connecting them with each other withOperator.AND
.UpdateConditionStep<R>
where(Field<Boolean> condition)
Add conditions to the queryUpdateConditionStep<R>
where(SQL sql)
Add conditions to the queryUpdateConditionStep<R>
whereExists(Select<?> select)
Add an EXISTS clause to the queryUpdateConditionStep<R>
whereNotExists(Select<?> select)
Add a NOT EXISTS clause to the query-
Methods inherited from interface org.jooq.Attachable
attach, configuration, detach
-
Methods inherited from interface java.util.concurrent.Flow.Publisher
subscribe
-
Methods inherited from interface org.jooq.Query
bind, bind, cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, poolable, queryTimeout
-
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 Detail
-
where
@Support UpdateConditionStep<R> where(Condition condition)
Add conditions to the query, connecting them with each other withOperator.AND
.
-
where
@Support UpdateConditionStep<R> where(Condition... conditions)
Add conditions to the query, connecting them with each other withOperator.AND
.
-
where
@Support UpdateConditionStep<R> where(Collection<? extends Condition> conditions)
Add conditions to the query, connecting them with each other withOperator.AND
.
-
where
@Support UpdateConditionStep<R> where(Field<Boolean> condition)
Add conditions to the query
-
where
@Deprecated @Support UpdateConditionStep<R> where(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Usewhere(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orwhere(Field)
instead. Due to ambiguity between calling this method usingField.equals(Object)
argument, vs. calling the other method via aField.equal(Object)
argument, this method will be removed in the future.Add conditions to the query
-
where
@Support @PlainSQL UpdateConditionStep<R> where(SQL sql)
Add conditions to the queryNOTE: 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:
DSL.condition(SQL)
,SQL
-
where
@Support @PlainSQL UpdateConditionStep<R> where(String sql)
Add conditions to the queryNOTE: 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:
DSL.condition(String)
,SQL
-
where
@Support @PlainSQL UpdateConditionStep<R> where(String sql, Object... bindings)
Add conditions to the queryNOTE: 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!
-
where
@Support @PlainSQL UpdateConditionStep<R> where(String sql, QueryPart... parts)
Add conditions to the queryNOTE: 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!
-
whereExists
@Support UpdateConditionStep<R> whereExists(Select<?> select)
Add an EXISTS clause to the query
-
whereNotExists
@Support UpdateConditionStep<R> whereNotExists(Select<?> select)
Add a NOT EXISTS clause to the query
-
-