db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-716) Re-enable VTIs
Date Thu, 03 May 2007 21:28:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493529

Rick Hillegas commented on DERBY-716:

Thanks, Dan and Army, for the continued discussion of the parameters to Function Tables.

Army and I seem to be concerned about different issues here. I am not concerned about the
type resolution of arguments to the Function Tables. This seems to me to be exactly the same
resolution logic which applies to existing (non-table) functions. I am not proposing to change
that logic. If the user guides don't adequately describe the type resolution of function arguments,
then that is another issue and it is someone else's itch.

I am concerned about the fact that certain expressions can appear in the arguments to non-table
functions but those expressions can not appear in the arguments to Function Tables. For instance,

select *
from T, TABLE( foo( T.a ) )
where bar( T.a ) = 3;

Here the expression T.a is a legal argument to bar() but not to foo().

I hope we are not talking past one another.

> 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.

View raw message