[jira] Assigned: (DERBY-3220) (ReferencingClause) in CREATE TRIGGER statement not SQL compliant

["Bernt M. Johnsen (JIRA)" <ji...@apache.org>]

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

Bernt M. Johnsen reassigned DERBY-3220:
---------------------------------------

    Assignee: Bernt M. Johnsen

> <transition table or variable list> (ReferencingClause) in CREATE TRIGGER statement not SQL compliant
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3220
>                 URL: https://issues.apache.org/jira/browse/DERBY-3220
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Bernt M. Johnsen
>            Assignee: Bernt M. Johnsen
>            Priority: Minor
>         Attachments: DERBY-3220.diff
>
>
> Derby implements the following syntax:
> REFERENCING
> {
> { OLD | NEW } [ AS ] correlation-Name [ { OLD | NEW } [ AS ] correlation-Name ] | 
> { OLD_TABLE | NEW_TABLE } [ AS ] Identifier [ { OLD_TABLE | NEW_TABLE }
> [AS] Identifier ] 
> }
> The SQL standard specifies:
> <trigger definition> ::=
> CREATE TRIGGER <trigger name> <trigger action time> <trigger event>
> ON <table name> [ REFERENCING <transition table or variable list> ]
> <triggered action>
> .......
> <transition table or variable> ::=
> OLD [ ROW ] [ AS ] <old transition variable name>
> | NEW [ ROW ] [ AS ] <new transition variable name>
> | OLD TABLE [ AS ] <old transition table name>
> | NEW TABLE [ AS ] <new transition table name>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.