db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: On DERBY-107 : ODBC Metadata functions
Date Thu, 27 Jan 2005 18:24:32 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Army wrote:

[a lot of stuff :-)]

I think VTI's are the wrong way to go. They are overkill I think for
what is required and will increase the static code footprint. In
addition there maybe platform issues where the correct type of result
set is needed to be returned for JSR169/JDBC2/JDBC3. It all depends on
exactly how the VTI (an implementation of ResultSet) would be handled in
the code.

I think that static modified queries based upon the JDBC queries are the
way to go. Since these can be created at derby compile time the
subsequent handling can be just like the existing JDBC meta-data
queries, rather than creating a new mechanism.

And as Lance pointed out, we need to maintain the JDBC metadata queries
in line with the spec, so no changing from INT to SMALLINT. Changes to
VARCHAR from CHAR I think are in line with the JDBC spec, as it defines
'String' as the type.

Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFB+THgIv0S4qsbfuQRAi4JAJ9sYBF1jYs2npMZAT70oViqCwhhvQCggukZ
1NXKTQymK9nIEF6DEcTmC7E=
=gDOK
-----END PGP SIGNATURE-----


Mime
View raw message