Re: !! Pro*C versus OCI !!

The main difference is that if OCI library is changed/updated the PRO*C compiler wil automatically take advantage of it without rewriting your code. You just need to recompilusing new version of PRO*C.

Additionally PRO*C seems to be a standard while OCI is a hacker's approach.

I found that C programmers prefer to use OCI function calls then use embeded SQL. However once they get used to the concept, it doesn't matter that much. Personally I prefer PRO*C.

I don't think however, that Oracle OCI is changed very often, but in the long run it can save couple of headaches.

                                        Edwin Kuprienko

Dennis Harvey (harvey_at_metropolis.com) wrote:
: Our company is presently porting one of our commercial applications
: from Sybase (OpenClient/DB-Library) to Oracle. I am inclined to go
: with the call level interface (OCI) rather that the precompiled
: approach (Pro*C). The OCI approach has the advantages of eliminating
: the need for the precompiler, and is easier to debug. Are there any
: compelling advantages to using the Pro*C approach? I appreciate any
: opinions or help I can get on this.
 

: Dennis Harvey
: Metropolis Software Inc.
: harvey_at_metropolis.com
 

-- 
------------------------------------------------------------
|     Whatever goes up has to go down.                     |
|     Whatever goes down will very likely stay that way.   |
------------------------------------------------------------