[
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-11-subqueries-aa.diff
Attaching derby-716-11-subqueries-aa.diff. This adds a test case to
TableFunctionTest, verifying that user-written table functions behave correctly
when invoked in subqueries with correlated references to outer query blocks.
> 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, derby-716-03-DatabaseMetaData-aa.diff,
> derby-716-04-Optimizer-aa.diff, derby-716-05-PublicAPI-aa.diff,
> derby-716-06-TestEncoding-aa.diff, derby-716-07-dblook-aa.diff,
> derby-716-08-upgrade-aa.diff, derby-716-09-upgradeLocalization-aa.diff,
> derby-716-10-datatypesCollation-aa.diff, derby-716-11-subqueries-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.
