On Wed, Apr 02, 2003 at 01:37:56PM +0200, Christian Mondrup wrote: > Tim Bunce wrote: > > file: $CPAN/authors/id/T/TI/TIMB/DBD-Oracle-1.14.tar.gz > > size: 199667 bytes > > md5: ec364509df5dfd57a4c05e2c410f358f > > > >=head1 Changes in DBD-Oracle 1.14 27th March 2003 > > > > NOTE: OCI 7 and Oraperl will not be supported in future releases. > > Sad to hear that since all Oracle perl scripts (and they are many) used > by my organization, Scandiatransplant are based on Oraperl. Probably the > majority of these scripts origin from good old perl4 oraperl days. > > Would it be possible to > > 1. after all keep supporting Oraperl or
I'll keep supporting Oraperl for anyone who keep paying me ;-) (FYI, no one pays me anything to support DBD::Oracle development. My current employer doesn't use it. It's all done on my own time and for no particular purpose as I don't even use it myself. The only income I've had from it is very occasional bit of consultancy, or payment for my time to add a specific feature.) Anyone wanting to establish a support contract for DBD::Oracle is invited to get in touch with me. > 2. to perform some "automagic" conversion of the scripts? There's nothing to stop you... a) not upgrading DBD::Oracle beyond 1.14 for systems using Oraperl. b) Copy and hack Oraperl.pm so it does a "use lib ...;" before a "use DBD::Oracle;" to load a separate DBD::Oracle <= 1.14 while still allowing non-Oraperl apps to use the latest DBD::Oracle. c) ... probably other variations on this theme ... Tim.
