On 1/24/06, Rob Kinyon <[EMAIL PROTECTED]> wrote: > According to the DBI docs under the description of the execute() > method, it says: > > If any arguments are given, then C<execute> will effectively call > L</bind_param> for each value before executing the statement.
...the key word being "effectively." I'm operating under the pleasant assumption (delusion? :) that what DBI does internally during execute() is more efficient than me calling through bind_param() repeatedly "from the outside." Maybe that's not the case, but I haven't had time to investigate. So far, the only need for bind_param() has been MySQL 5's new BIT type. I can imagine it being useful for other things down the line, and I even have a good idea of how to add support for it. But it's a significant code change, so if I can throw in a hack just to get the MySQL 5 BITs working right now, I'm happy to defer the work (and inevitable debugging). > The point behind bind_param() is that you're specifying the type for > the given parameter position for that $sth. You don't call it for > every execute() call. It has to be called for each prepare() (and even for each prepare_cached(), right?) which is the same thing. Obviously it's not called for each fetch(), which I think is what you meant. -John ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
