A page addresses a row of a server-side cursor by its position. When the cursor is rebuilt by a reload in another tab, a refresh or another user's change, the same position can hold a different record, and a button pressed on the old screen would act on the new one. The per-row CRC already detected a row that changed underneath. This release closes the other case: the row that is now a different record.
Tables: the record key travels with the request
- Identity brackets Fifteen endpoints that act on a row by position, including row actions, print, mail, threads, the navigator and child lists, now send the record's key. Under the row lock, the server confirms the record at that position is the one the key names before any work runs.
- An answer, not an error A mismatch is answered with HTTP
412and a structured body: the record the user was working on, the record now at that place, and the operation that was not done. The client opens one dialog with both records and a Reload button, in six languages. The server logs it as a warning, because it is an expected outcome. - Print and file the right rows A print sends the keys of the selected rows. Every one is checked before the PDF renders, and a one-row print is filed in the thread of the record that was printed, not the row the cursor stopped on.
Query views: the cursor is the identity
- One run, one UUID A query-backed view has no primary key, so every run of its statement builds a cursor with a new UUID. A button, a print of selected rows or a form script event sends the UUID of the rows the page shows in
X-Cursor-UUID, and the server compares it on arrival and again under the cursor's lock. - Unchanged rows still run A button also sends each selected row with its CRC. When the UUID differs but every named row is unchanged, the action runs. A changed, unloaded or missing row is refused with the message "the row changed since you saw it".
- Refresh keeps acting An in-place refresh takes the new rows and the new UUID together, so actions after a refresh keep working.
Each case was reproduced first as a failing test against Informix and on a demo test bed of patients and medication orders, then made to pass. A user who acts on a stale screen is now told so, with both records shown, instead of changing a record they never saw.