[DERBY-6475] Update documentation for SYSTRIGGERS after DERBY-5866 changes

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.11.1.1
• Fix Version/s: 10.12.1.1
• Component/s: Documentation
• Assignee: Myrna van Lunteren
• Reporter: Knut Anders Hatlen
• Created: 10/Feb/14 16:21
• Updated: 27/Nov/14 08:41
• Resolved: 27/Nov/14 08:41

Description

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.

Issue Links

• relates to: DERBY-5866 testFiringConstraintOrder(org.apache.derbyTesting.functionTests.tests.lang.TriggerTest)junit.framework.AssertionFailedError: matching triggers need to be fired in order creation:1,NO CASCADE BEFORE,DELETE,ROW