db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6475) Update documentation for SYSTRIGGERS after DERBY-5866 changes
Date Mon, 24 Nov 2014 20:32:12 GMT

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

Myrna van Lunteren commented on DERBY-6475:

I think perhaps going into version differences is too much detail for that table.
How about:
"Time the trigger was created, for internal use to ensure correct execution order of triggers."?

> Update documentation for SYSTRIGGERS after DERBY-5866 changes
> -------------------------------------------------------------
>                 Key: DERBY-6475
>                 URL: https://issues.apache.org/jira/browse/DERBY-6475
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
> DERBY-5866 changed the meaning of the SYS.SYSTRIGGERS.CREATIONTIMESTAMP column.
> Currently, the reference manual's mentioning of this columns says "Time the trigger was
> I suggest we add something similar to:
> "The time is stored in UTC if the trigger was created after upgrading to 10.11. Otherwise,
it is stored in the local time zone at the time the trigger was created. The primary purpose
of this column is to ensure the correct execution order of triggers, and the timestamp may
have been adjusted for that purpose, so applications should not rely on the accuracy of these
> Or maybe that's too much... "For internal use only" might suffice.

This message was sent by Atlassian JIRA

View raw message