You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/02/10 17:22:19 UTC
[jira] [Created] (DERBY-6475) Update documentation for SYSTRIGGERS
after DERBY-5866 changes
Knut Anders Hatlen created DERBY-6475:
-----------------------------------------
Summary: 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.0.0
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 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.1.5#6160)