[Helma-user] Java heap space in dbh.query()

[Maksim Lin for technical support mailling lists]

> > cachesize = 300000
> 
> This affects only the in-memory cache of HopObjects. If 
> anything, increasing it will lead to *more* memory problems.
> 
> -Joshua

Joshua is spot on - the cachesize setting is only for setting how many
HopObjects helma will cache when you use the builtin DB mapping
functionaly, not the maximum size of rresult sets when using the "raw"
scripted DB access object.
I would say that you will need *quite* a bit of memory if you need to
fetch sql results of 300000 rows! :-)
The docs here:
http://java.sun.com/j2se/1.5.0/docs/api/java/sql/ResultSet.html
provide a good start to find out how to use a cursor and non-updateble
result sets to help with large result sets using direct JDBC classes.

Maks.