[
https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493503
]
Daniel John Debrunner commented on DERBY-716:
---------------------------------------------
> A table function argument A[i] can be any expression whose corresponding JDBC
> type is the same
> as the JDBC type which corresponds to the SQL type of the function's declared
> parameter P[i].
Why is JDBC being mentioned here? Parameters for table functions are declared
as SQL types
and table functions are executed in SQL statements. There is no relationship to
JDBC.
JDBC only defines the mapping of the declared parameter type to the Java type,
it does not affect
the SQL compilation/binding.
> 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.
