On 15/11/10 14:15, Brian Phillips wrote: > On Nov 9, 9:43 am, bpphill...@gmail.com (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 would appreciate a clear up/down vote from someone in authority so > that I know how to proceed. > > Thanks, > Brian >
As far as I was aware, Tim has already said: "I think we should try to fix/workaround at least the SIGINT issue. The default behaviour should be to act in the most reasonable/useful way. An option could be provided to restore the current unreasonable way." so providing a patch which answers that criteria would be a good start. However, I, personally don't like the default behaviour changing when a) there is nothing wrong with my setup (or Charles' for that matter) b) if I remember correctly, only those people using Oracle 10 have seen an issue with SIGINT c) it would force ME to change my DBD::Oracle code when I don't have a problem and you, who does have a problem gets to make no changes! As a result, I would have less of an issue if you had to set a flag to change the default behaviour but I am only one tiny voice. Martin -- Martin J. Evans Easysoft Limited http://www.easysoft.com
