db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6109) Allow CREATE SYNONYM for table function invocations.
Date Fri, 22 Mar 2013 06:57:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610002#comment-13610002

Dag H. Wanvik commented on DERBY-6109:

Trying to grok that rationale for this, what would be the difference between a "wrapper view"
and this new mechanism? And how would it facilitate projection pushing?
> Allow CREATE SYNONYM for table function invocations.
> ----------------------------------------------------
>                 Key: DERBY-6109
>                 URL: https://issues.apache.org/jira/browse/DERBY-6109
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions:
>            Reporter: Rick Hillegas
> SYNONYMs are a non-standard extension supported by many databases. See DERBY-335. Right
now SYNONYMs are only allowed for tables and views. It would be useful (and should be easy)
to extend this feature to support SYNONYMs for table function invocations. E.g.:
> CREATE SYNONYM LT0_P for TABLE( LT0('with_provenance') )
> See the discussion of this topic on this email thread: http://apache-database.10148.n7.nabble.com/Limitations-of-Table-Functions-vs-old-VTIs-td127988.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message