add a diagram

2023-05-14 17:50:51 +02:00 · 2023-05-14 17:50:51 +02:00 · 86e40f619e
parent 37e8218227
commit 86e40f619e
2 changed files with 2 additions and 0 deletions
--- a/documentation/src/main/asciidoc/introduction/Tuning.adoc
+++ b/documentation/src/main/asciidoc/introduction/Tuning.adoc
@ -108,6 +108,8 @@ fundamental rule of thumb in ORM is:
 of a session/transaction, and fetch it immediately in one or two queries,
 - and only then start navigating associations between persistent entities.

+image:images/fetching.png[width=700,align="center"]
+
 Without question, the most common cause of poorly-performing data access
 code in Java programs is the problem of _N+1 selects_. Here, a list of N
 rows is retrieved from the database in an initial query, and then
--- a/documentation/src/main/asciidoc/introduction/images/fetching.png
+++ b/documentation/src/main/asciidoc/introduction/images/fetching.png