[
https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493550
]
Rick Hillegas commented on DERBY-716:
-------------------------------------
I searched the Derby codeline for all of the method names in VTIEnvironment.
They do not appear to be invoked anywhere although they are declared in the
VTIEnvironment interface itself and in FromVTI and in VTIResultSet.
There may be some value in exposing a vacuous VTIEnvironment interface, which
has no methods in it but which would be a placeholder for future expansion. I
don't see the value in retaining the existing, unused methods.
The unused getSharedState() and setSharedState() methods suggest that the whole
thing might be replaced with a Hashtable.
> 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.
