Re: TimeStamp Problem

Also, because when you absolutely, positively must have a unique key

but can't rely on a timestamp (even with 12 digit precision for the
second!) to provide it, what was the impetus to increase the
precision? Curious mind(s?) wants to know.

AFaIK the increased precision is similar to the effect for UUID whereby
the additional precision is not actual portions of time, but instead are
just [up to whatever is the precision beyond six] uniquely assigned values;
thus I suspect the TIMESTAMP with a sufficiently large precision [over
6-digits] would serve for UNIQUE values without having to depend on the
UUID.

Poking about in the IBM i 7.2 KnowledgeCenter I found the following
which may be the source for my above thinking:
<
https://www.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/sqlp/rbafydtts.htm

_Date, time, and timestamp data types_
"...
When the CURRENT TIMESTAMP special register or a variable with the
TIMESTAMP data type is used with a precision greater than 6, the timestamp
value is a combination of the system clock and uniqueness bits. The
uniqueness bits are assigned in an ascending order. Therefore, comparison
operations for timestamps with any precision will represent an accurate
order of when the timestamps were assigned.
..."

--
Regards, Chuck