in reply to Of large database tables and high memory usage.

executing the same query more times, using the limit/offset, can cause differend results. data can change between the queries unless you use an high isolation level (and in this case too, you can get an error instead of the data)

for what i know, anyway, the data is managed by the backend, and not dumped to the driver whiting the execute() call. or at least it is supposed to.

Oha

  • Comment on Re: Of large database tables and high memory usage.

Replies are listed 'Best First'.
Re^2: Of large database tables and high memory usage.
by mseabrook (Beadle) on Jul 30, 2007 at 23:06 UTC
    executing the same query more times, using the limit/offset, can cause differend results

    That's a really good point. So far I've only been using the strategy in scenarios where that wouldn't be an issue, but I'll have to keep it in mind if I want to make it a more general solution.