Re: $SIG{INT} tampering during DBI->connect on Oracle

2010-11-30 Thread John Scoles
On 30/11/2010 10:28 AM, Tim Bunce wrote: On Mon, Nov 15, 2010 at 10:04:56AM -0800, Brian Phillips wrote: - DBD::Oracle::db::_login($dbh, $dbname, $user, $auth, $attr) - or return undef; +{ +my @local_signals = @{ $attr->{ora_local_signals} || [] }; +local @s.

Re: $SIG{INT} tampering during DBI->connect on Oracle

2010-11-30 Thread Tim Bunce
On Mon, Nov 15, 2010 at 10:04:56AM -0800, Brian Phillips wrote: > - DBD::Oracle::db::_login($dbh, $dbname, $user, $auth, $attr) > - or return undef; > +{ > +my @local_signals = @{ $attr->{ora_local_signals} || [] }; > +local @s...@local_signals} if @local_signals; >

Re: $SIG{INT} tampering during DBI->connect on Oracle

2010-11-30 Thread John Scoles
On 30/11/2010 9:28 AM, Brian Phillips wrote: On Nov 15, 12:04 pm, bpphill...@gmail.com (Brian Phillips) wrote: See below for a patch that does not change the default behavior but allows the user to specify a list of signals to be localized during the connect phase. This could easily be default

Re: $SIG{INT} tampering during DBI->connect on Oracle

2010-11-30 Thread Brian Phillips
On Nov 15, 12:04 pm, bpphill...@gmail.com (Brian Phillips) wrote: > See below for a patch that does not change the default behavior but > allows the user to specify a list of signals to be localized during > the connect phase.  This could easily be default to localize the "INT" > handler but since