[
https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493538
]
Daniel John Debrunner commented on DERBY-716:
---------------------------------------------
VTIEnvironment was (is?) meant to be a general purpose class that provides some
control over & information for virtual tables, it was meant to be applicable to
more than costing, despite it's class javadoc. see how it is used on the other
interfaces that are applicable to virtual tables. Keeping the class may allow
future expansion, removing it would hinder future expansion.
isCompileTime() may provide useful state information if use of this class is
expanded in the future, though it may be ok to remove the method, since it
could be added back to the class at any time. Removing the class from the
methods passed to VTICosting would make it harder to add back in the future.
> 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
> Attachments: 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.
