$DBI::err not reset before connect_cached()
From: Jason E. Stewart (jason_at_openinformatics.com)
Date: 04/17/04
- Previous message: Tim Bunce: "Re: performance problem with dbd oracle"
- Next in thread: Tim Bunce: "Re: $DBI::err not reset before connect_cached()"
- Reply: Tim Bunce: "Re: $DBI::err not reset before connect_cached()"
- Reply: Tim Bunce: "Re: $DBI::err not reset before connect_cached()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: dbi-users@perl.org Date: 17 Apr 2004 18:34:15 +0530
Hey All,
Using DBI 1.41 and DBD::Pg 1.32 with mod_perl 1.29.0.2 and I get a
strange situation.
When I'm using a DB handle that ends in an error condtion, the next
time my mod_perl script calls connect_cached() if I check $DBI::err it
is still set to the last error that happend - not any error that
happened during the connect_cached() call - this leads to my connect
script thinking it got an error during the connect call, which isn't
true.
Do I need to be manually cleaning up DBI somehow? Or is this a bug?
Cheers,
jas.
- Previous message: Tim Bunce: "Re: performance problem with dbd oracle"
- Next in thread: Tim Bunce: "Re: $DBI::err not reset before connect_cached()"
- Reply: Tim Bunce: "Re: $DBI::err not reset before connect_cached()"
- Reply: Tim Bunce: "Re: $DBI::err not reset before connect_cached()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|