Michael,
Not entirely true.
Compatibility between the libs used in the client application (here
DBD::Oracle) and ORACLE_HOME should be 100%. I mean, they should be *exactly*
the same version. The slightest version difference is unsupported. If it works
otherwise, it's pure luck.
Compatibility between client application and target database is much more
lenient, and conforms to what you said.
Brgds,
Mark
"Michael A. Chase" wrote:
> The compatibility we need to worry about is between the DBD::Oracle we build
> and the version of Oracle pointed to by ORACLE_HOME. If they are
> compatible, the OCI handles the database communication, normally via
> SQL*Net. SQL*Net v2 (or 8) can talk to any Oracle database from 7.1 through
> 8.x (and probably 9i as well).
> --
> Mac :})
> ** I normally forward private database questions to the DBI mail lists. **
> Give a hobbit a fish and he'll eat fish for a day.
> Give a hobbit a ring and he'll eat fish for an age.
> ----- Original Message -----
> From: "Mark Vandenbroeck" <[EMAIL PROTECTED]>
> To: "Vincent Roquencourt" <[EMAIL PROTECTED]>
> Cc: "Tim Scott" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Tuesday, May 29, 2001 07:47
> Subject: Re: Connection pb with 2 oracle version! Please help!
>
> > If it works in that direction, it's pure luck. After all, it's not because
> we
> > make a new version, that we make EVERYTHING incompatible :-)
> >
> > Vincent Roquencourt wrote:
> >
> > > Thanks guys!!! it works this way BUT... (there's is always one).. the
> > > strange thing is that the same script works if i compile DBI /DBD with
> the
> > > lowest oracle version (7.3.4).Why? Do we have upward (and not backward)
> > > compatibility?
> > >
> > > (FYI , it also works connecting via OCI and bypassing tnsnames.ora file
> with
> > > 7.3.4' compiled DBI but i won't use it for update :) )
--
Mark Vandenbroeck Mobile : +32-495-59.55.62
Business Process Manager Email : [EMAIL PROTECTED]
EMEA Support Information Systems AIM : markvdb
