Re: Re: Re: Re: Re: accessing Apache::DBI 'cached connections'

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Re: accessing Apache::DBI 'cached connections' by bobn (Chaplain) on Jul 21, 2003 at 21:58 UTC
Agreed. Unless you're really diligent, turning on RaiseError is better. You can always wrap in an eval when you rally want somthing other than death. I turn on RaiseError. ;-/ --Bob Niederman, http://bob-n.com	[reply]
Re: Re: Re: Re: Re: Re: accessing Apache::DBI 'cached connections' by geektron (Curate) on Jul 21, 2003 at 22:20 UTC
yes, agreed. i thought i was getting info from the startup.pl .. but that doesn't seem to be the case. maybe subject for different node ... but i've preloaded CGI::Carp ... `# Tell me more about warnings use CGI::Carp qw( fatalsToBrowser warningsToBrowser ); $SIG{__WARN__} = \&Carp::cluck;` [download] but i'm not getting the fatalsToBrowser behaviour i'm supposed to ... normal 500 error messages, not Carp output	[reply] [d/l]
Re: Re: Re: Re: Re: Re: Re: accessing Apache::DBI 'cached connections' by perrin (Chancellor) on Jul 21, 2003 at 22:31 UTC
If you mean that you aren't getting the same connection that you tried to set up in startup.pl, that's because you aren't sending in the same connection parameters. They have to be identical. CGI::Carp is kind of a hack and people often have trouble with it.	[reply]