[
https://issues.apache.org/jira/browse/DERBY-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen closed DERBY-6475.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.12.0.0
Assignee: Myrna van Lunteren
Thanks, Myrna. The fix looks good to me. Closing the issue.
> 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: 10.11.1.1
> Reporter: Knut Anders Hatlen
> Assignee: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.12.0.0
>
> Attachments: DERBY-6475.diff, rrefsistabs79888.html
>
>
> 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 created".
> 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
> values."
> Or maybe that's too much... "For internal use only" might suffice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
