Hi all, we are currently using DBD::ORACLE 1.16 and DBI 1.46, and I'm having a
tough time
trying to determine if either of these are still supported by the open source
community.
All help is appreciated.
Thanks,
Gary
On 23/01/12 14:13, TIDWELL, GARY wrote:
Hi all, we are currently using DBD::ORACLE 1.16 and DBI 1.46, and I'm having a
tough time
trying to determine if either of these are still supported by the open source
community.
All help is appreciated.
Thanks,
Gary
DBI 1.46 isn't even on cpan now
I would have to agree with Martin. The bigest jump, code-wise was the jump
between 16~17 so you are very much out of luck if you want to get anything
fixed in 16 or eariler. I you update to 17 first and see what happens you will
get a good idea if you can update any futher. I also depends on
If I remember what the docs told me (we recently went through an upgrade
from 9i to 10g), any thing pre 1.26 can work with anything up to 9i. 1.26
and later can work 9i and 10g however 11g and 12 will not work unless you
upgrade further.
I THINK I have that right.. However the DBD::Oracle documen
I'm sorry I should clarify.. When I say "work" I mean you can build it
against that version of the OCI.
What you should do is see what the highest version of the DBD::Oracle can
build against your OCI client.
Carl Furst
On 1/23/12 10:32 AM, "Furst, Carl" wrote:
>If I remember what the doc
Thanks for the quick response.
Sounds like you've answered my question, but I will go ahead and explain
my situation.
We are using the old versions because we never had an issue
or moved to a version of Perl or Oracle that needed us to change. If we did we
would
have upgraded at that time.
W
On 23/01/12 15:36, TIDWELL, GARY wrote:
Thanks for the quick response.
Sounds like you've answered my question, but I will go ahead and
explain my situation.
We are using the old versions because we never had an issue or moved
to a version of Perl or Oracle that needed us to change. If we did
