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

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

On 1/26/06, Amaury Forgeotdarc <Ama...@gl...> wrote:
> Anthony Tuininga wrote:
> > 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.
>
> The same risk already exists with every Oracle application,
> even when explicitely linked with a specific Oracle oci.lib,
> even the current cx_Oracle:
>
> When loading a DLL, Windows checks every function by its name,
> but has no way to check for the number or type of the arguments
> (unless they use the C++ call convention, which encodes the
> types in the function name).
>
> Actually, the "shadow functions" we are about to write are
> very close to the code embedded when linking with oci.lib.
>
> As long as there is a file named oci.dll, Oracle will have to
> ensure compatibility between releases.

Ok, I can accept that the risks are reasonable. The only other
difference in behavior that I can think of is that some of the current
differences between OCI releases are based on #define constants --
which are definitely not available in the dll. We will need to find
some function that exists in one release and not in the other and use
the presence of that function instead as a means of determining what
client level is being used. Are you volunteering to find those??? :-)
Are you volunteering to provide the template I should be using to try
this? How eager are you to move down this path?

> --
> Amaury Forgeot d'Arc
> Ubix Development
> www.ubitrade.com
>
>
> -------------------------------------------------------
> 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
>