DATAJPA-1793 - Introduce the term "custom method".
This commit is contained in:
@@ -550,7 +550,7 @@ If the underlying database or the JPA implementation supports additional wildcar
|
||||
=== Modifying Queries
|
||||
|
||||
All the previous sections describe how to declare queries to access a given entity or collection of entities.
|
||||
You can add custom modifying behavior by using the facilities described in "`<<repositories.custom-implementations>>`".
|
||||
You can add custom modifying behavior by using the custom method facilities described in "`<<repositories.custom-implementations>>`".
|
||||
As this approach is feasible for comprehensive custom functionality, you can modify queries that only need parameter binding by annotating the query method with `@Modifying`, as shown in the following example:
|
||||
|
||||
.Declaring manipulating queries
|
||||
@@ -567,7 +567,7 @@ Doing so triggers the query annotated to the method as an updating query instead
|
||||
If you wish the `EntityManager` to be cleared automatically, you can set the `@Modifying` annotation's `clearAutomatically` attribute to `true`.
|
||||
|
||||
The `@Modifying` annotation is only relevant in combination with the `@Query` annotation.
|
||||
Derived query methods or custom methods do not require this Annotation.
|
||||
Derived query methods or custom methods do not require this annotation.
|
||||
|
||||
[[jpa.modifying-queries.derived-delete]]
|
||||
==== Derived Delete Queries
|
||||
|
||||
Reference in New Issue
Block a user