Re: DBD::mysql and mysql_use_result

On Sat, 7 Aug 2004, Patrick Galbraith wrote:

> As far as use_result vs. store result, the server prepared statements 
> (mysql 4.1 and greater) will always use 'store result', as this has no 
> affect on performance as per the API documentation.
> 

I plan, if possible, to make "use result" the default with prepared statements,
my thinking here is this: if you are going to be using parepared statements, you
will more than likly be running in a persistant envionment, in which case,
memory usage becomes more of an issue. esp. in something like a mod_perl
envionment because when you use "store result" you will more than likely use 2x
the memory (or more) -- Think of an application that munges the result result
set and pases the munged data off to a templating system for a total of three
times memory usage of just the result set.  

And from my reading of the docs (though I have not had a chance to test this 
yet), mysql_stmt_store_result() need not be called mysql_stmt_fetch(). Is this 
the case?


Rudy


-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/[email protected]