- All Superinterfaces:
Attachable
,AttachableQueryPart
,Delete<R>
,DeleteFinalStep<R>
,DeleteLimitStep<R>
,DeleteOrderByStep<R>
,DeleteReturningStep<R>
,DMLQuery<R>
,Flow.Publisher<Integer>
,Publisher<Integer>
,org.reactivestreams.Publisher<Integer>
,Query
,QueryPart
,RowCountQuery
,Serializable
,Statement
- All Known Subinterfaces:
DeleteUsingStep<R>
Delete
's DSL API.
Example:
DSLContext create = DSL.using(configuration);
create.delete(table)
.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 DeleteConditionStep<R>
Add conditions to the query.@NotNull DeleteConditionStep<R>
Add conditions to the query.@NotNull DeleteConditionStep<R>
Add conditions to the query.@NotNull DeleteConditionStep<R>
where
(Collection<? extends Condition> conditions) Add conditions to the query, connecting them with each other withOperator.AND
.@NotNull DeleteConditionStep<R>
Add conditions to the query, connecting them with each other withOperator.AND
.@NotNull DeleteConditionStep<R>
Add conditions to the query, connecting them with each other withOperator.AND
.@NotNull DeleteConditionStep<R>
Add conditions to the query.@NotNull DeleteConditionStep<R>
Add conditions to the query.@NotNull DeleteConditionStep<R>
whereExists
(Select<?> select) Add an EXISTS clause to the query.@NotNull DeleteConditionStep<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 org.jooq.AttachableQueryPart
getBindValues, getParam, getParams, getSQL, getSQL
Methods inherited from interface org.jooq.DeleteLimitStep
limit, limit
Methods inherited from interface org.jooq.DeleteOrderByStep
orderBy, orderBy, orderBy
Methods inherited from interface org.jooq.DeleteReturningStep
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
Methods inherited from interface org.reactivestreams.Publisher
subscribe
Methods inherited from interface org.jooq.Query
bind, bind, cancel, execute, executeAsync, executeAsync, isExecutable, keepStatement, poolable, queryTimeout
-
Method Details
-
where
Add conditions to the query, connecting them with each other withOperator.AND
. -
where
Add conditions to the query, connecting them with each other withOperator.AND
. -
where
@NotNull @CheckReturnValue @Support @NotNull DeleteConditionStep<R> where(Collection<? extends Condition> conditions) Add conditions to the query, connecting them with each other withOperator.AND
. -
where
Add conditions to the query. -
where
Add conditions to the query.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!
- See Also:
-
where
Add conditions to the query.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!
- See Also:
-
where
@NotNull @CheckReturnValue @Support @PlainSQL @NotNull DeleteConditionStep<R> where(String sql, Object... bindings) Add conditions to the query.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!
-
where
@NotNull @CheckReturnValue @Support @PlainSQL @NotNull DeleteConditionStep<R> where(String sql, QueryPart... parts) Add conditions to the query.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!
-
whereExists
Add an EXISTS clause to the query. -
whereNotExists
@NotNull @CheckReturnValue @Support @NotNull DeleteConditionStep<R> whereNotExists(Select<?> select) Add a NOT EXISTS clause to the query.
-