Re: Java heap space in dbh.query()

Julian Tree wrote:
> there are still some stored procedure and trigger running in the 
> PostgreSQL backend.  So using the helma ORM is not an option.

I would not think triggers would be an insurmountable obstacle to using 
the ORM--or even an obstacle at all in many cases. But I also don't know 
if it would be advisable to use the ORM in this case anyway. Unless 
there's a way to tell Helma not to cache at all a collection of 
HopObject children (which I don't know yet), it would eat your whole 
HopObject cache a few times over.