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

Subject: Re: 5250 and un-do -- ROW CHANGE TOKEN warning
From: Arco Simonse <arco400@xxxxxxxxx>
Date: Fri, 22 Dec 2017 16:58:14 +0100
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Literally every table in our erp system has a ROW CHANGE TIMESTAMP column.
All of our web apps get the rctokens on read and post them back to the
backend when content is saved. And we have found that a great way to ensure
that records have not changed in the meanwhile.

Regards,
-Arco

Op vrijdag 22 december 2017 heeft Raul Jager <raul@xxxxxxxxxx> het volgende
geschreven:

The initial reason to suggest row change is to know if the row has
changed between the time it was read to display and the time it is read
to update.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.