db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-534) Support use of the WHEN clause in CREATE TRIGGER statements
Date Thu, 24 Oct 2013 12:13:02 GMT

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

Knut Anders Hatlen updated DERBY-534:
-------------------------------------

    Attachment: derby-534-14-a-remove-formatable-upgrade.diff

I've convinced myself that TriggerDescriptor instances are only written to disk as part of
TriggerInfo instances in stored prepared statements. Since Derby always clears all SPSs on
version change, one version of Derby will never try to read an instance written by another
version of Derby. (TriggerInfo even has a comment that says "since this is something that
is used in stored prepared statements, it is ok to change it if you make sure that stored
prepared statements are invalidated across releases.")

derby-534-14-a-remove-formatable-upgrade.diff removes the code that makes TriggerInfo and
TriggerDescriptor instances compatible across versions.

Note that the patch only changes the upgrade logic for trigger descriptors written using the
Formatable interface. The logic that adds a column to the SYS.SYSTRIGGERS table on upgrade
is not touched by the patch.

All regression tests, including all upgrade tests, ran cleanly with the patch.

> Support use of the WHEN clause in CREATE TRIGGER statements
> -----------------------------------------------------------
>
>                 Key: DERBY-534
>                 URL: https://issues.apache.org/jira/browse/DERBY-534
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Kristian Waagan
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>              Labels: derby_triage10_11
>         Attachments: derby-534-01-a-syntax.diff, derby-534-02-a-refactor.diff, derby-534-03-a-npe-testcase.diff,
derby-534-04-a-referencing.diff, derby-534-05-a-generated-cols.diff, derby-534-06-a-temptables.diff,
derby-534-07-a-more-restrictions.diff, derby-534-08-a-test-invalidation.diff, derby-534-09-a-drop-column-deps.diff,
derby-534-09-b-drop-column-deps.diff, derby-534-10-a-get-sps.diff, derby-534-11-a-more-tests.diff,
derby-534-12-a-subquery-npe.diff, derby-534-13-a-dblook.diff, derby-534-14-a-remove-formatable-upgrade.diff,
parser.diff, WhenClause.html, WhenClause.html, WhenClause.html, WhenClause.html, WhenClause.html
>
>
> Support use of the WHEN clause in CREATE TRIGGER statements. The clause is described
in the SQL standard (2003) in chapter "11.39 <trigger definition>" under "<triggered
action>".
> There are traces in the code that suggests some work has been done on this earlier. If
anyone knows something about this, please add a comment to this issue.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message