Re: OCI playing nice with Pro*C QUESTION

A copy of this was sent to "Alan Kierstead" <akierstean_at_cfl.rr.com> (if that email address didn't require changing) On Wed, 22 Mar 2000 00:55:26 GMT, you wrote:

>Here's the scenario:
>
>Using Oracle 8.1x on Solaris 2.6 writing in C.
>
>I have a set of APIs which nicely handle all connecting to the database
>using OCI calls.
>I have a separate function in a shared object that does updates to
>a BLOB column using Pro*C.
>
>problem:
>I'd love to have an application which used the OCI APIs to connect
>to the database, and still use the Pro*C library calls to do my update
>of the BLOB column using the connection from OCI, but I can't find
>documentation on how to accomplish this in any of Oracle's docs.
>Unfortunately it appears that Pro*C won't automatically pick up the
>connection established by OCI, and explicitly logging in through
>Pro*C causes a second connection to be established which
>invalidates the "single unit of work" idea I'm trying to maintain here.
>
>Anyone ever tried it this way?
>

It doesn't go that way. A proc app can call OCI functions. An oci app (connection done by OCI) cannot then call proc (proc must initiate the connection).

>btw, I can certainly use OCI to do the BLOB updates, but for several
>work-related reasons I'd like to have the implementation available using
>Pro*C as well...
>
>If you need any more info I'll be happy to provide it...
>
>thx in advance
>
>AcK
>

-- 
http://osi.oracle.com/~tkyte/
 
Thomas Kyte                   tkyte_at_us.oracle.com
Oracle Service Industries     Reston, VA   USA

Opinions are mine and do not necessarily reflect those of Oracle Corporation