document implicit joins in 'delete'/'update' queries

Signed-off-by: Gavin King <gavin@hibernate.org>
This commit is contained in:
Gavin King 2024-04-27 00:35:10 +02:00
parent 8eebf0bafb
commit f55f1c7a43
1 changed files with 8 additions and 2 deletions

View File

@ -314,7 +314,10 @@ Adding the keyword `versioned`—writing `update versioned`—specifies that Hib
update versioned Book set title = :newTitle where ssn = :ssn update versioned Book set title = :newTitle where ssn = :ssn
---- ----
Unfortunately, an `update` statement may not directly join other entities, not even using an <<implicit-join,implicit join>>, but it may have subqueries in its `set` clause, or in the `where` clause, which may contain joins. An `update` statement may not directly `join` other entities, but it may:
- have an <<implicit-join,implicit join>>, or
- have subqueries in its `set` clause, or in its `where` clause, and the subqueries may contain joins.
[[delete]] [[delete]]
==== Delete statements ==== Delete statements
@ -343,7 +346,10 @@ A `delete` statement is executed by calling `Query.executeUpdate()`.
The integer value returned by `executeUpdate()` indicates the number of entity instances affected by the operation. The integer value returned by `executeUpdate()` indicates the number of entity instances affected by the operation.
A `delete` statement may not directly join other entities, but it may have subqueries in the `where` clause, which may contain joins. A `delete` statement may not directly `join` other entities, but it may:
- have an <<implicit-join,implicit join>>, or
- have subqueries in its `where` clause, and the subqueries may contain joins.
[[insert]] [[insert]]
==== Insert statements ==== Insert statements