Changing the database through the "back door" is in contradiction to using a orm especially with a cache.

I would try to avoid this situation completely (although I know that you have needs for it).

A solution using the back door cold be:


Send a notification to the application using hibernate.
This Notification leads to an eviction of the cache (Probably the notification can contain infromation about the part of the cache to be evicted).


Force JPA to load database changes in background
How can I change the location of the log file in PostgreSQL? Can it be done without stopping the cluster?
