CriteriaDelete
- Type Parameters:
- <T>- the entity type that is the target of the DELETE
- Super Interfaces:
- CommonAbstractCriteria
 The 
CriteriaDelete interface defines functionality for performing bulk delete operations using the Criteria API Criteria API bulk delete operations map directly to database delete operations. The persistence context is not synchronized with the result of the bulk delete.
 A CriteriaDelete object must have a single root. 
- Since:
- JPA 2.1
Public Methods
 A 
CriteriaDelete object has a single root, the entity that is being deleted. - Parameters:
- entityClass- the entity class
- Return:
- query root corresponding to the given entity
- Since:
- JPA 2.1
 A 
CriteriaDelete object has a single root, the entity that is being deleted. - Parameters:
- entity- metamodel entity representing the entity of type X
- Return:
- query root corresponding to the given entity
- Since:
- JPA 2.1
 Returns empty set if there are no parameters. Modifications to the set do not affect the query. 
- Return:
- the query parameters
- Inherited from:
- CommonAbstractCriteria
- Since:
- JPA 2.1
- Parameters:
- type- the subquery result type
- Return:
- subquery
- Inherited from:
- CommonAbstractCriteria
- Since:
- JPA 2.1
- Parameters:
- type- the subquery result type
- Return:
- subquery
- Inherited from:
- CommonAbstractCriteria
- Since:
- JPA 2.1
 Replaces the previously added restriction(s), if any. 
- Parameters:
- restriction- a simple or compound boolean expression
- Return:
- the modified delete query
- Since:
- JPA 2.1
 Replaces the previously added restriction(s), if any. If no restrictions are specified, any previously added restrictions are simply removed. 
- Parameters:
- restrictions- zero or more restriction predicates
- Return:
- the modified delete query
- Since:
- JPA 2.1