File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed
documentation/src/main/asciidoc/userguide/chapters/caching Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -263,7 +263,7 @@ This is useful for frequently executed queries with fixed parameter values.
263
263
264
264
[NOTE]
265
265
====
266
- Caching of query results introduces some overhead in terms of your applications normal transactional processing.
266
+ Caching of query results introduces some overhead in terms of your application's normal transactional processing.
267
267
For example, if you cache results of a query against `Person`,
268
268
Hibernate will need to keep track of when those results should be invalidated because changes have been committed against any `Person` entity.
269
269
@@ -392,7 +392,7 @@ include::{example-dir-caching}/SecondLevelCacheTest.java[tags=caching-query-regi
392
392
[[caching-query-cache-layout]]
393
393
=== Query cache layout
394
394
395
- The query cache usually contains the same data that is read from the original queries JDBC `ResultSet`,
395
+ The query cache usually contains the same data that is read from the original query's JDBC `ResultSet`,
396
396
but for entities and collections the cached information can vary depending on configuration.
397
397
398
398
An entity or collection in the query cache can either be represented with all its fetched data (`FULL` cache layout),
You can’t perform that action at this time.
0 commit comments