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

You might find Re: DBI + 'SELECT *' - Memory Use Galore? useful.

  • 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 27, 2007 at 19:28 UTC

    Apparently my Super Search skills aren't up to snuff. :/

    That node is indeed useful to me. Thanks!

Re^2: Of large database tables and high memory usage.
by doom (Deacon) on Jul 29, 2007 at 19:18 UTC
    Thanks for posting this pointer. I was tremendously confused by this question myself... I could've sworn that DBI was architected to avoid this problem. You shouldn't get an entire result set unless you do a "fetchall" of some sort, and if you want to process the set row by row you use a "fetchrow". Just doing an "execute" shouldn't be placing any burden on the client...

    This appears to be yet-another mysql gotcha... they do something really lame by default to make their server performance look better.