I am using torque in an application which deals with thousands of records, maybe eventually millions. As far as I can tell the only way to iterate through them is using the standard ArrayList from the doSelect method. This of course doesn't get me very far before I run out of memory.
Why doesn't torque implement it's own List subclass instead of using an ArrayList when selecting multiple records? This way it could internally avoid having to keep all of the rows in memory at the same time. The ArrayList implementation looks very Micky-Mouse. Another alternative is to have methods that return an iterator rather than a list, in the vast majority of cases where you only need sequential access. How are other people dealing with these limitations?
