Hibernate/hibernate-orm
1
0
Fork 0
mirror of https://github.com/hibernate/hibernate-orm synced 2025-02-16 16:15:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

mention path-based matching in section on @Find methods

Browse Source
This commit is contained in:
Gavin King 2023-07-15 00:17:38 +02:00
parent 57e47e0ba1
commit 06ed2072ce
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
documentation/src/main/asciidoc/introduction/Generator.adoc
View File

@ -459,6 +459,15 @@ public List<Book> getBooksByTitle(String title, Type type) {
} }
---- ----
It's even possible to match a parameter of a finder method against a property of an associated entity or embeddable.
The natural syntax would be a parameter declaration like `String publisher.name`, but because that's not legal Java, we can write it as `String publisher$name`, taking advantage of a legal Java identifier character that nobody ever uses for anything else:
[source,java]
----
@Find
List<Book> getBooksByPublisherName(String publisher$name);
----
A finder method may specify <<fetch-profiles,fetch profiles>>, for example: A finder method may specify <<fetch-profiles,fetch profiles>>, for example:
[source,java] [source,java]

2
documentation/src/main/asciidoc/introduction/Introduction.adoc
View File

@ -613,7 +613,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. 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. 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`. The JPA-standard property is `jakarta.persistence.schema-generation.database.action`.