Tim - > So I assume this class will cover the "cursor handling" for me, right? Correct.
> Does it make a difference for the DelegatingResultList class if I use its iterator or can I also use the get(int index) method within a for loop without performance/ memory penalties? Honestly, it's been quite some time since I've used the LRS support.... so you'll need to do some experimentation to make sure that iterator vs get(index) work as expected. HTH, Rick On Mon, May 30, 2011 at 8:57 AM, tfriess <[email protected]> wrote: > > Rick Curtis wrote: > > > > Tim - > > > > Take a look at Large Result Sets[1]. > > > > [1] > > > http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_dbsetup_lrs > > > > Thanks, > > Rick > > > > -- > > *Rick Curtis* > > > > Hello Rick, > thank you for your fast response and thanks for the hint! > > Using a Debugger I see that the List implementation returned by the Querys > "getResultList()" method is a "DelegatingResultList". So I assume this > class > will cover the "cursor handling" for me, right? > (I always thought getResultList would simply return an ArrayList or > something like this.) > > Does it make a difference for the DelegatingResultList class if I use its > iterator or can I also use the get(int index) method within a for loop > without performance/ memory penalties? > So can I use the following constructs without concerns? > List theList = ... > for(MyObject o : theList) { > ... > } > > or > > for(int i = 0; i != theList.size(); ++i) { > ... > } > > Thank you! > -- *Rick Curtis*
