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

Hi Vern.

Yes I know that. Just wanted to point out that this is not possible for
columns that are defined with FOR EACH ROW ON UPDATE AS ROW CHANGE
TIMESTAMP.
Trying to define these with (12) is not allowed.

Best regards,
-Arco

Op donderdag 21 december 2017 heeft Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
het volgende geschreven:

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."

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD