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] [Updated] (DERBY-5779) Table functions should only accept arguments which are constant in their query block.
Date Fri, 13 Jul 2012 19:57:34 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rick Hillegas updated DERBY-5779:

    Attachment: derby-5779-04-aa-subqueriesInFromList.diff

Attaching derby-5779-04-aa-subqueriesInFromList.diff. This is the first rev of a patch to
forbid the problem identified above with subqueries in the FROM list. This patch is not ready
for commit. I need to add more test cases and run regression tests.
> Table functions 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:
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For:
>         Attachments: derby-5779-01-ab-forbidReferencesInQueryBlock.diff, derby-5779-02-aa-forbidReferencesToJoinedTables.diff,
derby-5779-03-aa-moreTests.diff, derby-5779-04-aa-subqueriesInFromList.diff, releaseNote.html
> Derby lets you invoke a table function 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.

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


View raw message