db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmars...@Sourcery.Org>
Subject Re: On DERBY-107 : ODBC Metadata functions
Date Mon, 24 Jan 2005 12:50:03 GMT
Hash: SHA1

RPost wrote:
> For any given instance of EDM will a user potentially be calling both
> "getColumns" and "getColumnsForODBC"?  Your comments for option II (add a
> protected variable "forODBC) seem to imply that only one or the other will
> get called.
> If only one set of queries will be executed it there may be a 4th option:
>     change the metadata.properties load process to load the version
> This could be done in a static block when the driver is first loaded by
> adding an option to the URL at connect time.

I don't think this would work as a single network server (derby
instance) might have both JDBC and ODBC clients. These clients would
call the Stored Procedures with the appropriate options setting for what
they need. Also we found a while back when we had two metadata files,
one for embedded and one for network server that we had a lot of
maintenance issues associated with the slightly different queries.
I'll post a separate response to Army's mail.

An example of how we currently branch based on the options can be seen
in the SQLTables function of:

I'll send a separate response to Army's mail.

Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


View raw message