I am not sure, but I think the problem you have is that Apache::DBI ignores
any disconnect() calls on database handles, and doesn't actually disconnect.
- Original Message -
From: "Jordan McLain" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, October 10, 2006 10:57 PM
Subject: DESTROY
I ha
>
>I am not sure, but I think the problem you have is that Apache::DBI ignores
>any disconnect() calls on database handles, and doesn't actually disconnect.
That's true.Apache::DBI ignores all the disconnect() calls.
--
Jeff Pang
NetEase AntiSpam Team
http://corp.netease.com
Dondi M. Stroma wrote:
I believe that since $db is a global variable it's not going to be
destroyed. If you got rid of the 'use vars' and changed it to
sub handler {
my $r = shift;
my $db = eCarList::DB->new();
...
}
then it would be.
This is absolutely the correct change.
--
---
I have the call to the module in a block already.
It goes something like:
package eCarList::Admin;
use eCarList::DB;
use eCarList::Output;
use vars qw($db);
sub handler {
my $r = shift;
$db = eCarList::DB->new();
}
On 10/11/06, Tyler Bird <[EMAIL PROTECTED]> wrote:
Try
uot; <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 11, 2006 12:06 PM
Subject: Re: Re: DESTROY
I have the call to the module in a block already.
It goes something like:
package eCarList::Admin;
use eCarList::DB;
use eCarList::Output;
use vars qw($db);
sub handler {
my $r = sh
Good call, thanks for the help guys. I really appreciate it.
Jordan
On 10/11/06, Philip M. Gollucci <[EMAIL PROTECTED]> wrote:
Dondi M. Stroma wrote:
> I believe that since $db is a global variable it's not going to be
> destroyed. If you got rid of the 'use vars' and changed it to
>
> sub ha
That is not the problem... The problem comes in when I do not use
Apache::DBI and I still end up with alot of mysql threads. The
problem is that I do not think DESTROY is being called.
On 10/10/06, Jordan McLain <[EMAIL PROTECTED]> wrote:
That is not the problem... The problem comes in when I
If I were you, I would put something like
warn "I'm being destroyed.";
in the DESTROY method, so you'll know for sure whether that is the case.
- Original Message -
From: "Jordan McLain" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, October 10, 2006 1
Sent: Tuesday, October 10, 2006 11:20 PM
Subject: Re: Re: Re: DESTROY
> That is not the problem... The problem comes in when I do not use
> Apache::DBI and I still end up with alot of mysql threads. The
> problem is that I do not think DESTROY is being called.
>
> On 10/10/06,
On Tue, 2009-09-15 at 14:29 -0500, David Nicol wrote:
> I'm ignorant of internals specifics, but perl's full cleanup on exit
> needs to be called, and is called at an orderly shutdown. It doesn't
> get called at POSIX::exit, or when the process in which the
> interpreter is embedded exits without c
Quoting [EMAIL PROTECTED]:
> Hi Fella's,
>
(..)
>
>
Oops, think I should have told ya something more on why I think DESTROY is not
handled. Well, that's very easy to say: The lines printed to STDERR from within
the DESTROY function do not appear in my error_log. Though this:
[EMAIL PROTECTED] li
On Sat, Jul 10, 2004 at 11:33:44AM +0200, [EMAIL PROTECTED] wrote:
> Oops, think I should have told ya something more on why I think DESTROY is not
> handled. Well, that's very easy to say: The lines printed to STDERR from within
> the DESTROY function do not appear in my error_log. Though this:
H
Quoting Wouter van Vliet <[EMAIL PROTECTED]>:
> >
> > Hi Wouter,
> >
> > Did you check the manual[1]? This reference is for Apache::PerlRun but
> > it may give you some ideas of why you're seeing that behavior.
> >
> >
> > Good luck,
> > William
> >
> > [1]
>
http://perl.apache.org/docs/1.0/guide/
>
> Hi Wouter,
>
> Did you check the manual[1]? This reference is for Apache::PerlRun but
> it may give you some ideas of why you're seeing that behavior.
>
>
> Good luck,
> William
>
> [1]
http://perl.apache.org/docs/1.0/guide/porting.html#Apache__PerlRun__a_closer_look
>
Thank you very muc
14 matches
Mail list logo
