Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

improved reasoning around nullability of finder method parameters

This commit is contained in:
Gavin King 2023-07-15 20:54:01 +02:00 committed by Christian Beikov
parent 0f39de8e65
commit 159189f4f9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -100,9 +100,9 @@ But it's something to watch out for.
If you're completely new to Hibernate and JPA, you might already be wondering how the persistence-related code is structured.
Well, typically, your persistence-related code comes in two layers:
Well, typically, our persistence-related code comes in two layers:
. a representation of your data model in Java, which takes the form of a set of annotated entity classes, and
. a representation of our data model in Java, which takes the form of a set of annotated entity classes, and
. a larger number of functions which interact with Hibernate's APIs to perform the persistence operations associated with your various transactions.
The first part, the data or "domain" model, is usually easier to write, but doing a great and very clean job of it will strongly affect your success in the second part.