Hey all,

I have a large DB table I need to insert into and was therefore using session.createSQLQuery() to avoid having to load the collection to do this. This however seems to invalidate all my caches. I know that it has no effect on any of them. How can I prevent the caches from being invalidated?

Cheers,

Dan

You could get the sessions connection and insert using straight JDBC (Note: the API is/has changed in this area). Alternatively, I would look at the type of mapping that you have for the collection so you can avoid loading all of it.

Hi David,

Thanks for your help. We have considered using straight JDBC but would prefer to find a hibernate solution. Can you suggest any mappings that won't load the entire collection upon update?

Cheers,

Dan.

If refactoring the data model is an option, you can create a new entity that represents the relationship itself then simply do a one-to-many on that. You can then persist new ones without triggering a full collection load.

See reference docs for bi-directional mapping of a collection using a bag. This can be updated without the collection being initialised.

see http://www.hibernate.org/hib_docs/v3/reference/en/html/performance.html#performance-collections-mostefficientupdate