Re: OCI future anybody?

From: Scott Urman <surman_at_dlsun338.us.oracle.com>
Date: 1996/07/22
Message-ID: <4t0d4a$n1i_at_inet-nntp-gw-1.us.oracle.com>#1/1


In article <31F2DFE4.69EA_at_lvalue.com>, Vladimir Stavitsky <vlads_at_lvalue.com> writes:
|> Hi, everybody.
|> We have an OCI based C++ class library; last night we were installing
|> it on Oracle 7.3 on Solaris 2.5; we ran into some problems during
|> link time, which were able to resolve after reading some docs which
|> came with Oracle.
|>
|> Unfortunately, the docs we read, while helpful, explained what we
|> need in a section "Unsupported features", which is kind of frightening.
|> Does this mean that in 7.4 OCI is doomed?

Of course not. It sounds like your class library is using some of the deprecated functions. OCI is continually being enhanced, and new functions are added that replace old ones. As this is done, the old functions are considered 'deprecated' and moved to the back of the manual. For the next major release, they are considered obsolete, and are removed from the library.

For example, the osql3() function is the V6 parsing function. It is replaced by oparse() in Oracle7. osql3() is still in the O7 library, but it won't be in Oracle8. osql() (the V5 function) is in the V6 library, but not the O7 one. Maintainers of OCI programs should be upgrading them along with Oracle to get the current functionality and enhancements.

|>
|> Thanks
|>
|> Vlad
|> --
|> ---------------------------------------------------------------------
|> ... occurrences like this will be few and far between ...
|>
|> vlads_at_webvalue.com Vlad Stavitsky vlads_at_lvalue.com
|> ---------------------------------------------------------------------



Scott Urman Oracle Corporation surman_at_us.oracle.com

Author of _Oracle PL/SQL Programming_ ISBN 0-07-882176-2 Published by Oracle Press - http://www.osborne.com/oracle/index.htm

"The opinions expressed here are my own, and are not necessarily that of  Oracle Corporation"
Received on Mon Jul 22 1996 - 00:00:00 CEST

Original text of this message