I need to re-integrate disconnect back into Apache::DBI managed
connections
my choices are either:
a- do it in some hacktastical manner that is useful only to me, but
takes 20 minutes to implement
b- do it as an actual reintegration/patch to Apache::DBI that others
can use , but takes w
On Thu, 2006-05-25 at 18:32 -0400, Jonathan Vanasco wrote:
> I need to re-integrate disconnect back into Apache::DBI managed
> connections
What problem are you trying to solve? You might find it more useful to
replace Apache::DBI with DBI->connect_cached. Keep in mind though, you
will have to
On May 25, 2006, at 6:52 PM, Perrin Harkins wrote:
What problem are you trying to solve? You might find it more
useful to
replace Apache::DBI with DBI->connect_cached. Keep in mind though,
you
will have to take care of not opening connections during startup and
doing safety rollbacks in a
On Thu, 2006-05-25 at 19:18 -0400, Jonathan Vanasco wrote:
> closing read-only connections opened / closed at startup
Connections opened during startup shouldn't be persisted by Apache::DBI.
Maybe you've found a bug.
> depending on the project's load order, Apache::DBI is sometimes
> loaded bef
> On Thu, 2006-05-25 at 19:18 -0400, Jonathan Vanasco wrote:
> > closing read-only connections opened / closed at startup
>
> Connections opened during startup shouldn't be persisted by Apache::DBI.
> Maybe you've found a bug.
>
There is indeed a bug under Apache 2 - I submitted a patch for this
perhaps its a bug. i don't know.
basically, i have this:
BEGIN
{
use MyApp::DB::Config;
my $DB_config = MyApp::DB::Config->new();
$DB_config->dbconnect(); # connects and stores a dbh in a wrapper
class $DB_config->{'DBH'}
=snip
pull some startup config vars
=
Clinton Gormley wrote:
On Thu, 2006-05-25 at 19:18 -0400, Jonathan Vanasco wrote:
closing read-only connections opened / closed at startup
Connections opened during startup shouldn't be persisted by Apache::DBI.
Maybe you've found a bug.
There is indeed a bug under Apache 2 - I submitted a pa
