Im using the process level JCS cache pretty heavily
against a very static database that mainly consists
of a single common table with a dozen "detail" tables.

My understanding is that Hibernate (2.0.2) will maintain
a cache for Main, each of the Detail classes and
one per collection relationship between Main and Detail.

Is there a way to make it dumber than this and just leave
the HashSet between sessions?

ie JCS region just for Main and cached instances of Main keep
a tree of objects (even those loaded by Hibernate)?

Seems to me like it would give small but significant performance
advantage. I could cache it outside HIbernate but then Id lose
the ability to mix and match what is cached and what isnt.

Anyway, to the developers: fantastic code, many thanks.

Cheers

Sam

There's a number of good reasons for the current design. Most importantly we can't just cache a set of objects; we have to disassemble the set and cache just the ids.

This will not be changed.

Thanks for reply.

Wasnt asking for change in the design (seems very
elegant and powerful).

Just wondering if any way to tell it to dumb down :)

Thanks

Sam