[
https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493553
]
Rick Hillegas commented on DERBY-716:
-------------------------------------
Maybe the VTICosting instantiator could have a signature like this and it would
be up to the implementation to throw a SQLException if there isn't enough
information to cost the VTI:
public static VTICosting getVTICosting
(
String schemaName, // table function's schema as declared at
CREATE FUNCTION time
String tableFunctionName, // table function's name as declared at
CREATE FUNCTION time
HashMap functionArguments // key = arg name from CREATE FUNCTION, value =
bind() time value, possibly null if bind() can't figure it out
)
throws SQLException;
> 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.
