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

  On 15/11/2010 9:15 AM, Brian Phillips wrote:
> On Nov 9, 9:43 am, [email protected] (Brian Phillips) wrote:
>> In my opinion, adding an option to change the current behavior is low
>> risk and completely satisfactory for resolving my issue while leaving
>> current behavior unchanged.  If there are concerns that this may be
>> affecting others, perhaps it would make sense to change the default
>> behavior but this is not something I'm asking for.
> So, can I expect anything from DBD::Oracle in this regard?  Can we
> provide a DBI->connect attribute to enable the functionality I'm
> requesting?  I will supply a patch if that would help.  My only other
> options is to start lobbying for changes in higher-level modules like
> DBIx::Class or to maintain a CPAN Distroprefs patch file for our
> installation of DBD::Oracle here at $WORK, neither of which is as
> clean of a solution as getting this added into DBD::Oracle.
>
I can add in an 'ora_' type attribute that could take care of it.  I 
have done it for other little things as well.
I do not think this will go against the spec in any way.

You can send me the patch and I will apply it.

It would be nice to have a generic solution to this problem but I do not 
see how this is possible as any solution would have to cover so many OS 
and client versions we would never get them all?

So I am in favour.

one thumbs up:)
> I would appreciate a clear up/down vote from someone in authority so
> that I know how to proceed.
>
> Thanks,
> Brian
>