Menu
I am using Hibernate and Spring for my web application.
In database operation, Hibernate is caching entities and returning them in next request without reading the actual database. I know this will reduce the load on database and improve performance.
But while this app still under construction, I need to load data from database in every request (testing reason).
Is there any way to force database read?
I became sure about the caching from this log4j message.
Returning cached instance of singleton bean 'HelloController' DEBUG [http-bio-8080-exec-42] - Last-Modified value for [/myApp/../somePageId.html] is: -1 
239
But Hibernate invalidates the 2nd level cache if you execute an SQL UPDATE or DELETE statement as a native query. This is necessary because the SQL statement changed data in the database, and by that, it might have invalidated entities in the cache. By default, Hibernate doesn't know which records were affected.
As with most other fully-equipped ORM frameworks, Hibernate has the concept of a first-level cache. It's a session scoped cache which ensures that each entity instance is loaded only once in the persistent context. Once the session is closed, the first-level cache is terminated as well.
Hibernate also implements a cache for query resultsets that integrates closely with the second-level cache. This is an optional feature and requires two additional physical cache regions that hold the cached query results and the timestamps when a table was last updated.
You can extend this caching with an optional second-level cache. The first-level keeps being mandatory and is consulted first always. The second-level cache is used to cache object across sessions.
session.refresh(entity) or entityManager.refresh(entity) (if you use JPA) will give you fresh data from DB.
62
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
