Interface QueryMapper.MapperDeleteWhere
- All Superinterfaces:
QueryMapper.MapperDeleteQueryBuild
- Enclosing interface:
QueryMapper
Represents a step where it is possible to compose delete conditions using
logical conjunctions or disjunctions, or execute the built delete query.
This step is reached after a delete condition has been defined and allows
combining additional conditions using and(...) or or(...),
or finalizing the operation by executing the query.
@Inject
Template template;
template.delete(Book.class)
.where("author").eq("Ada")
.and("publishedYear").gte(2020)
.execute();
The returned instance is mutable and not thread-safe.
Support for logical operators depends on the capabilities of the underlying
NoSQL database.- Since:
- 1.0.0
-
Method Summary
Modifier and TypeMethodDescriptionCreates a new delete condition using logical conjunction (AND) by specifying a column name.Creates a new delete condition using logical disjunction (OR) by specifying a column name.Methods inherited from interface QueryMapper.MapperDeleteQueryBuild
execute
-
Method Details
-
and
Creates a new delete condition using logical conjunction (AND) by specifying a column name.template.delete(Book.class) .where("author").eq("Ada") .and("publishedYear").gte(2020) .execute();- Parameters:
name- the column name- Returns:
- the
QueryMapper.MapperDeleteNameConditionwith the delete condition appended - Throws:
NullPointerException- when name is null
-
or
Creates a new delete condition using logical disjunction (OR) by specifying a column name.template.delete(Book.class) .where("author").eq("Ada") .or("author").eq("Hermann") .execute();- Parameters:
name- the column name- Returns:
- the
QueryMapper.MapperDeleteNameConditionwith the delete condition appended - Throws:
NullPointerException- when name is null
-