Hi,

I've a quite complex piece of buissness-logic which executes quite a lot of database queries and because of that is painfully slow.
What I've done in some areas is to replace database-queries with HashMaps, fetching all data at the beginning into a HashMap,
and looking up the actually needed result by key. However thats a really bad thing for code-quality and maintainability :/

Is there some way to make hibernate re-use the results from an already executed query, if its obvious that it already has all the looked-up'ed items loaded before?

Something like:


Thank you in advance, Clemens

You can use the second level cache and then make your query cacheable by calling query.setCacheable(true).

Yes, but that only works if you execute the same query over and over, which is not the case.

You can use filters to narrow your resultset, but you are asking that Hibernate should interpreter your query and figure out if it should or should not execute, that's up to yourself.

Hibernate does make sure not to load the same entity 2 times using the session cache.

Hi Dencel,

Do you know whats the "standard"-way of solving the too-many-queries-because-of-too-oop-heavy-code?
My code is OOP-heavy, e.g. calculating one item at a time - and because of the complexity of the buissness logic I don't dare to mess arround and destroy its structure.

Thanks, Clemens

no, it's way more powerful. make sure you make the entities cacheable by PK, and collection relations cacheable, and queries too.

I'll give it a try - Thanks!

- Clemens