Re: C interface: Pro*C/C++, OCI, Microsoft Visual C++ 6.0 integration
Date: 5 Oct 2002 05:50:36 -0700
Message-ID: <233b7a65.0210050450.35ec86fa_at_posting.google.com>
"Jacob Laursen" <jlu_at_no-spam-kmd.dk> wrote in message news:<3d9d44a8$0$96750$edfadb0f_at_dspool01.news.tele.dk>...
> Which interface is recommended to use when communicating with an Oracle
> database from Microsoft Visual C++? Currently I use embedded SQL in
> Pro*C/C++, but have a feeling that this method is obsolete (and a scary
> feeling that Oracle might even drop support for it).
I don't believe Oracle recommends one approach over another-- there are strengths & weaknesses to each. I'd be shocked to learn that Pro*C was headed for the scrapheap-- unless your feeling is the result of some official Oracle documentation, I'd ignore it.
If you have a bunch of Pro*C code that's working now and you're comfortable with Pro*C, I think you'd be nuts to rewrite everything.
> Before changing a lot
> of code, I'd like to know if OCI is the way to go now? As I understand, this
> would make it possible to explicitly supply a handle to a transaction
> object, thus making it possible to share a transaction object with a
> PowerBuilder application.
OCI doesn't have "transaction handles"-- it does have a number of handles for connections, sessions, service contexts, etc. I'm not sure what you mean by "transaction handle", so I cannot say that tbis is impossible, but I've never heard of Powerbuilder and another application sharing a session.
Justin Cave Received on Sat Oct 05 2002 - 14:50:36 CEST