Hi,

Looking at the Session API, one notices that it is possible to selectively load, save and delete specific objects. However, the flush() method indiscriminately synchronizes the cache with the underlying database.

This poses problem for the application I'm working on since we would like to be able to flush changes that happened on specific objects only, not all dirty objects found in the cache. Is there a way to accomplish this ? Is there a clear reason why flush() isn't selective, and if not can we expect that it could become selective in future Hibernate releases ?

Thanks in advance for a response,
Louis-Frederic Huppe-St-hilaire

There are three ways to selectively synchronize state with the database that I know of:

1. Use the session-per-request pattern (close session on each request). Load the objects on one request and save them in another. This means that most of the time you will be working with detached objects (objects that are not known to the session--objects become detached when the session is closed). You can call session.save( ), session.update( ), etc. in a subsequent request on the objects you want synchronized, and leave the others detached.

2. Evict (detach) the objects that you do not want persisted

3. Use multiple sessions. Only flush the session that you want synchronized