#110586Record history rollback writes two unrelated correlation ids
Description
RecordHistoryRollback::performRollback() runs up to two DataHandler instances — one for the command map (undelete / delete), one for the data map(field values) — and passes no CorrelationId to either start() call.
Each instance therefore generates its own random correlation scope, so a single logical rollback ends up as two unrelated scopes in sys_history. The undelete half and the field-restore half of the same rollback cannot be recognised as one operation, and there is no way to tell later which entries a rollback produced.
Expected: create one CorrelationId in performRollback() and hand it to both DataHandler::start() calls.
Reviews 3
History 14
-
Gerrit Code Review pushed patch set 1 for main to change 95536 status
NewUnder Review <span data-processor="relativetime" data-value="2026-09-01T21:04:00+00:00" > 09/01/26, 21:04 </span> -
Gerrit Code Review pushed patch set 1 for 14.3 to change 95544 <span data-processor="relativetime" data-value="2026-09-02T06:57:40+00:00" > 09/02/26, 06:57 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 95545 <span data-processor="relativetime" data-value="2026-09-02T06:57:46+00:00" > 09/02/26, 06:57 </span>
-
Benni Mack commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-09-02T07:00:10+00:00" > 09/02/26, 07:00 </span>
Applied in changeset commit:3e0703d7d0b1a9d4920ea8a760d53266a681427d.