how about just calling clear() on the session after each "cache less" work you need ?

/max

Andrea Aime wrote:
On Friday 15 August 2003 06:15, [EMAIL PROTECTED] wrote:

I guess it would be easily possible to turn the cache *off*.

But what do you do about circular references?

You get exposed to stack overflows w/o a cache.


Uh, I see, maybe just keep a statement-local list of known object ids (if already saved don't do it again to break the loop)
Maybe, if the cache can be factored out as a separate class, a special version that manages only
ids for the duration of a single statement can be used (just thinking out loud,
I didn't had a look at the code).


Andrea



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel



------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to