Hibernate/hibernate-orm
1
0
Fork 0
mirror of https://github.com/hibernate/hibernate-orm synced 2025-02-09 04:34:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

update docs for StatelessSession to reflect new capabilities

Browse Source
This commit is contained in:
Gavin King 2024-12-31 18:59:30 +01:00
parent 59f772f3a0
commit 813f76b70f
2 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -870,7 +870,7 @@ StatelessSession ss = getSessionFactory().openStatelessSession();
A stateless session: A stateless session:
- doesn't have a first-level cache (persistence context), nor does it interact with any second-level caches, and - doesn't have a first-level cache (persistence context), and
- doesn't implement transactional write-behind or automatic dirty checking, so all operations are executed immediately when they're explicitly called. - doesn't implement transactional write-behind or automatic dirty checking, so all operations are executed immediately when they're explicitly called.
For a stateless session, we're always working with detached objects. For a stateless session, we're always working with detached objects.

6
documentation/src/main/asciidoc/userguide/chapters/batch/Batching.adoc
View File

@ -125,8 +125,7 @@ However, it is good practice to close the `ScrollableResults` explicitly.
Thus, a stateless session is a slightly lower-level abstraction that's closer to the underlying JDBC activity: Thus, a stateless session is a slightly lower-level abstraction that's closer to the underlying JDBC activity:
* there's no first-level cache, * there's no first-level cache, and
* the stateless session does not interact with any second-level or query cache, and
* there's no transactional write-behind or automatic dirty checking. * there's no transactional write-behind or automatic dirty checking.
Instead, persistence operations occur synchronously when a method of `StatelessSession` is invoked, and entities returned by a stateless session are always detached. Instead, persistence operations occur synchronously when a method of `StatelessSession` is invoked, and entities returned by a stateless session are always detached.
@ -140,9 +139,8 @@ With a stateless session, there's no need to explicitly manage the size of the f
The `StatelessSession` API comes with certain limitations: The `StatelessSession` API comes with certain limitations:
* operations performed using a stateless session never cascade to associated instances, * operations performed using a stateless session never cascade to associated instances,
* collections are ignored by a stateless session,
* lazy loading of associations is not transparent, and is only available via an explicit operation named `fetch()`, and * lazy loading of associations is not transparent, and is only available via an explicit operation named `fetch()`, and
* operations performed via a stateless session bypass Hibernate's event model and interceptors. * operations performed via a stateless session bypass Hibernate's event model and action queue.
IMPORTANT: Due to the lack of a first-level cache, stateless sessions are vulnerable to data aliasing effects. IMPORTANT: Due to the lack of a first-level cache, stateless sessions are vulnerable to data aliasing effects.