mention path-based matching in section on @Find methods

This commit is contained in:
Gavin King 2023-07-15 00:17:38 +02:00 committed by Christian Beikov
parent 38c0844b66
commit 3d0c0782f5
1 changed files with 1 additions and 1 deletions

View File

@ -670,7 +670,7 @@ So, since most persistence logic written using Hibernate 6 is _extremely_ portab
We do need to be careful here if our persistence code uses native SQL, or if it uses concurrency-management features like pessimistic locks.
====
Whether we're testing against your real database, or against an in-memory Java database, we'll need to export the schema at the beginning of a test suite.
Whether we're testing against our real database, or against an in-memory Java database, we'll need to export the schema at the beginning of a test suite.
We _usually_ do this when we create the Hibernate `SessionFactory` or JPA `EntityManager`, and so traditionally we've used a <<automatic-schema-export,configuration property>> for this.
The JPA-standard property is `jakarta.persistence.schema-generation.database.action`.