2010/11/25 Benoît Minisini <gam...@users.sourceforge.net>: >> good evening all, >> i have another question about my eternal punishment: the result object :-) >> >> caveat answered to a former question about results in general: >> >If you got into the habit of reading all the >> >records you've selected into memory (or even if the Result object >> >worked >> >that way behind the scenes...), you'd soon find everything breaking >with >> >Out Of Memory errors as soon as you start doing anything serious. >> >> my question now is, how the result works behind the scenes, is there a >> counter (result.index?) that tells a layer (the driver?) which record is >> to be given back? >> >> regards, >> tobi >> > > A result object stores the entire query of the result in memory, because of > the stupidity of most SQL backends. Postgresql definately supports cursors (being able to retrieve rows in groups and not hold them all in memory)
Ian ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
