[
https://issues.apache.org/jira/browse/DERBY-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290246#comment-13290246
]
Dag H. Wanvik commented on DERBY-5779:
--------------------------------------
Sounds like a good plan to me. As long as we can't express the intent of the
query in another way (maybe recursive SQL would enable it?), *and* we can
define the semantics precisely, I guess we could retain the syntax for VTIs.
> Table functions and vtis should only accept arguments which are constant in
> their query block.
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-5779
> URL: https://issues.apache.org/jira/browse/DERBY-5779
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.1.0
> Reporter: Rick Hillegas
>
> Derby lets you invoke a table function/vti in the FROM list of a query,
> passing in arguments built out of columns in other tables in the FROM list.
> This syntax is illegal and the resulting queries have no meaning under the
> SQL Standard. See the discussion on DERBY-5554. We should forbid this syntax.
> Similar syntax involving correlated subqueries in the FROM list is already
> forbidden. Fixing this will create a backward incompatibility which requires
> a release note. In particular, the sample usage for SYSCS_DIAG.SPACE_TABLE,
> given in the Reference Manual, will no longer work after fixing this bug.
> Changes to SPACE_TABLE are being discussed on DERBY-5554.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
