10 messages in com.mysql.lists.perlRe: backup subroutine| From | Sent On | Attachments |
|---|---|---|
| case...@yahoo.com | 11 Sep 2003 11:47 | |
| Rudy Lippan | 11 Sep 2003 12:09 | |
| Greg Meckes | 11 Sep 2003 12:10 | |
| case...@yahoo.com | 11 Sep 2003 12:37 | |
| Ulrich Borchers | 11 Sep 2003 12:52 | |
| case...@yahoo.com | 11 Sep 2003 13:15 | |
| Rudy Lippan | 11 Sep 2003 13:29 | |
| Ulrich Borchers | 11 Sep 2003 14:01 | |
| case...@yahoo.com | 11 Sep 2003 14:05 | |
| case...@yahoo.com | 11 Sep 2003 14:15 |
| Subject: | Re: backup subroutine![]() |
|---|---|
| From: | case...@yahoo.com (case...@yahoo.com) |
| Date: | 09/11/2003 02:05:38 PM |
| List: | com.mysql.lists.perl |
If I understood, when mysql_use_result is 1, the result is not passed to client until it is fetched. Where is it stored then?
--- Rudy Lippan <rlip...@remotelinux.com> wrote:
On Thu, 11 Sep 2003, case...@yahoo.com wrote:
Date: Thu, 11 Sep 2003 13:15:37 -0700 (PDT) From: "case...@yahoo.com" <case...@yahoo.com> To: pe...@lists.mysql.com Subject: Re: backup subroutine
Yes, this is better I think. But the problem with memory consumption persists when I "SELECT * FROM $table". The result is stored somewhere by DBI or DBI::mysql until it's fetched from there.
Other solution may be to count rows first, then estimate if there are millions of rows add LIMIT n,m and execute SELECT few times. It sounds quite complicated.
Or you can use mysql_use_result so that DBD::mysql does not store the results of the query client side.
Rudy
-- MySQL Perl Mailing List For list archives: http://lists.mysql.com/perl To unsubscribe: http://lists.mysql.com/perl?unsub=case...@yahoo.com
__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com




