Fix a couple of typo's
Signed-off-by: Jan Schatteman <jschatte@redhat.com>
This commit is contained in:
parent
e7c3f52499
commit
f65f393a01
|
@ -263,7 +263,7 @@ This is useful for frequently executed queries with fixed parameter values.
|
|||
|
||||
[NOTE]
|
||||
====
|
||||
Caching of query results introduces some overhead in terms of your applications normal transactional processing.
|
||||
Caching of query results introduces some overhead in terms of your application's normal transactional processing.
|
||||
For example, if you cache results of a query against `Person`,
|
||||
Hibernate will need to keep track of when those results should be invalidated because changes have been committed against any `Person` entity.
|
||||
|
||||
|
@ -392,7 +392,7 @@ include::{example-dir-caching}/SecondLevelCacheTest.java[tags=caching-query-regi
|
|||
[[caching-query-cache-layout]]
|
||||
=== Query cache layout
|
||||
|
||||
The query cache usually contains the same data that is read from the original queries JDBC `ResultSet`,
|
||||
The query cache usually contains the same data that is read from the original query's JDBC `ResultSet`,
|
||||
but for entities and collections the cached information can vary depending on configuration.
|
||||
|
||||
An entity or collection in the query cache can either be represented with all its fetched data (`FULL` cache layout),
|
||||
|
|
Loading…
Reference in New Issue