Re: 5250 and un-do -- ROW CHANGE TOKEN warning

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Arco

As we've discussed in other posts in this thread, SQL now can handle the 
12-decimals of a timestamp, and this does guarantee uniqueness in those 
last 6 places, although not actual time values.

I think!

Vern

On 12/21/2017 11:49 AM, Arco Simonse wrote:
> As a sidenote: Even when the table has a column defined with ROW CHANGE
> TIMESTAMP (which is always a TIMESTAMP (6) datatype), its uniqueness is not
> guaranteed.
>
> Best regards,
> -Arco
>
> Op donderdag 21 december 2017 heeft Mark S Waterbury <
> mark.s.waterbury@xxxxxxxxxxxxx> het volgende geschreven:
>
> > Justin,
> >
> > Relying on DB2 "ROW CHANGE TOKEN" if the table does not have a ROW CHANGE
> > TIMESTAMP column is risky, as there exists the possibility of "false
> > negatives."