Re: [cx-oracle-users] RE: Re: Choosing client libraries

[Anthony T. <ant...@gm...>]

On 1/25/06, Amaury Forgeot d'Arc <ama...@gm...> wrote:
> Anthony wrote:
> > Ok. It sounds like a bunch of grunt work but nothing particularly
> > difficult. There is the necessity of "copying" the Oracle header files
>
> Not necessarily. You may require that compiling a cx_Oracle distribution
> needs the latest Oracle header files for the module to contain all featur=
es.
>
> Then, when installed on another machine, the module will silently
> disable some features if they do not match the Oracle version.

What I meant is that shadow functions will have to be defined which
call the real functions. These will look very similar to the ones
defined in the Oracle include files. If/when such things change those
changes will have to be reflected. Note that this technique assumes
that Oracle __never__ changes or removes their API for a particular
function. They only add functions. I'm not convinced this will always
be the case which makes this technique somewhat of a risk -- fairly
low but still a risk.

> > and there is the question of performance as well. Any thoughts on
> > those?
>
> Well, if the code is carefully written and uses inline functions,
> the overhead could be reduced to a simple check on a static
> variable.

True. The only overhead would be during import or first reference of a
particular function and that would be relatively small.

> --
> Amaury
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> cx-oracle-users mailing list
> cx-...@li...
> https://lists.sourceforge.net/lists/listinfo/cx-oracle-users
>