Description
Tech support can use the DatabaseMetaData wrapper functions to answer questions about Derby metadata. Today some of those questions can't be answered easily because we have not implemented the SQL Information Schema. The functions can be found attached to DERBY-3973. An email thread discussed how to productize these functions: http://old.nabble.com/productizing-the-metadata-wrapper-functions-to30428490.html#a30428490 Consensus developed around the following points:
1) The DatabaseMetaData wrappers are useful to Derby developers and to tech support.
2) The wrappers are lightweight enough to be bundled in the engine jar.
3) We do not want to create new compatibility guarantees for Derby. Therefore, the functions should not be exposed in Derby's public api and should not be documented in the user guides.
The following approach makes some sense:
A) Put the wrappers in Derby's diag package.
B) Make it possible to register and invoke diag methods which load and unload the wrappers.
C) Use the Derby wiki to document how tech support can use these wrappers.
D) Be prepared to remove these wrappers when we implement the Information Schema.
Attachments
Issue Links
- relates to
-
DERBY-3973 Create function wrappers for DatabaseMetaData so that you can join metadata results in queries.
- Closed
-
DERBY-6022 Add a system procedure for (un)registering optional packages of Derby tools.
- Closed