On 8/17/07, Perrin Harkins <[EMAIL PROTECTED]> wrote: > Do you think that Apache::DBI should be doing this on every connect > call to begin with? I suppose it depends on whether it is trying to > provide safety for ported CGI scripts, or a general purpose persistent > database connection.
Exactly. Right now, it considers each connect() call a "new beginning", which may or may not be appropriate, depending on the context. > Actually, that might be a simple fix for this: If you call > DBI->connect, Apache::DBI would do what it does now. If you call > connect_cached, it would skip the reset call. What do you think? I've always found it odd that DBI has explicit hooks for Apache::DBI, but I suppose DBI's internals kind of dictate that. Anyway, if you can change how Apache::DBI behaves in response to DBI->connect vs. DBI->connect_cached, then I think making connect_cached() return the existing handle "untouched" (again, maybe with a ping check as per the usual rules) would be appropriate. -John ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
