db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (DERBY-6387) Incorrect ordering of triggers in dblook
Date Wed, 26 Feb 2014 22:43:24 GMT

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

Mike Matrigali reopened DERBY-6387:

      Assignee: Mike Matrigali  (was: Knut Anders Hatlen)

temp assign to myself while working on backport to 10.10.

> Incorrect ordering of triggers in dblook
> ----------------------------------------
>                 Key: DERBY-6387
>                 URL: https://issues.apache.org/jira/browse/DERBY-6387
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Mike Matrigali
>             Fix For:
>         Attachments: create-triggers.sql, d6387-1a.diff
> The order in which triggers fire, is partly determined by the order in which they are
> See here:
> http://db.apache.org/derby/docs/10.10/ref/rrefsqlj43125.html
> |   When multiple triggers are defined for the same database event for
> |   the same table for the same trigger time (before or after), triggers
> |   are fired in the order in which they were created.
> And here:
> SQL:2003, part 2, section 4.38.1 General description of triggers:
> |   The order of execution of a set of triggers is ascending by value of
> |   their timestamp of creation in their descriptors, such that the
> |   oldest trigger executes first.
> Since the order of creation matters, dblook should generate CREATE TRIGGER statements
in an order that preserves the original order of execution.
> dblook currently generates CREATE TRIGGER statements in the order returned by a SELECT
query against SYS.SYSTRIGGERS. The SELECT query does not have an ORDER BY clause, so it is
not guaranteed to return the rows in a specific order.

This message was sent by Atlassian JIRA

View raw message