[
https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-716:
--------------------------------
Attachment: derby-716-02-DatabaseMetaData-aa.diff
Attaching derby-716-02-DatabaseMetaData-aa.diff. This patch adds TableFunction
support to our implementation of DatabaseMetaData.getFunctions() and
getFunctionColumns(). Touches the following files:
M java/engine/org/apache/derby/catalog/types/RoutineAliasInfo.java
Add a new method so that metadata queries can determine whether a function is a
TableFunction.
M java/engine/org/apache/derby/impl/jdbc/metadata.properties
M java/engine/org/apache/derby/catalog/GetProcedureColumns.java
Amend the queries and the dbproc which provide the results for getFunctions()
and getFunctionColumns().
M
java/shared/org/apache/derby/shared/common/reference/JDBC40Translation.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/TableFunctionTest.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestDbMetaData.java
M java/testing/org/apache/derbyTesting/junit/JDBC.java
Regrssion tests.
The regression tests ran cleanly for me under Java 6 except for the outstanding
orphaned ResultSet problem in ProcedureInTriggerTest. That test runs cleanly
standalone. This is the same regression test behavior seen in DERBY-2983.
> Re-enable VTIs
> --------------
>
> Key: DERBY-716
> URL: https://issues.apache.org/jira/browse/DERBY-716
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-716-01-basic-aa.diff,
> derby-716-02-DatabaseMetaData-aa.diff, functionTables.html,
> functionTables.html, functionTables.html
>
>
> Cloudscape used to expose Virtual Table Interfaces, by which any class which
> implemented ResultSet could be included in a query's FROM list. Derby still
> exposes a number of these VTIs as diagnostic tools. However, Derby now
> prevents customers from declaring their own VTIs. The parser raises an error
> if a VTI's package isn't one of the Derby diagnostic packages.
> This is a very powerful feature which customers can use to solve many
> problems. We should discuss the reasons that it was disabled and come up with
> a plan for putting this power back into our customers' hands.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
