Issue Bug Under Review

#91980Database "tstamp" field of nestet record wrong

Christian Hackl 08/11/20, 16:39 updated 11/13/26, 08:34

Description

if you have nested elements in a record, i.e. several and you edit one element of these nested elements. Then the tstamp is reset for all these nested elements.

expectation:
tstamp should only be set for those records where a change was made / which was edited.

————
In the exmaple (image) i change the last record and safe the parent, then all 3 records have the new tstamp value.

Reviews 1

Files 1

History 412

  1. Benni Mack commented and changed status New Accepted <span data-processor="relativetime" data-value="2025-08-29T14:41:55+00:00" > 08/29/25, 14:41 </span>

    OK. The culprit for this is in RelationHandler->writeForeignField() as this does not check if we actually need to update the record at all.

    We could do a check if we need to update the records actually, which would actually save a LOT of queries when persisting!

  2. Gerrit Code Review pushed patch set 1 for main to change 92429 status Accepted Under Review <span data-processor="relativetime" data-value="2026-01-20T16:17:58+00:00" > 01/20/26, 16:17 </span>