TYPO3 Core

Hey Jürgen,

thanks for your report. I guess we would need to check if the history (sys_history) is added there as well (this is usually an info that the record was modified).

Hi Jürgen, nice to read from you here again :)

From an EventSourcing point of view (we don't have EventSourcing in the core) I totally get to point to check what has changed and only process/project those changes - e.g. trigger rendering of pages that were changed or warm-up their caches again.

Usually the meaning of "tstamp" was "modified by editor" which actually would not be the case when the sorting value was updated because some other record was inserted and sorting values had to be reprocessed.

I need to think a little bit about potential implications...

Hi Oli,
there are several code examples inside the DataHandler-class, where the tstamp (of a none editor changed DB-record) is updated. The "position" where i added the logic to update the tstamp was only the last one, which didn't contain such a logic. Man könnte also sagen, dass durch meinen Fix die Logik (zum updaten des tstamps) in der DataHandler-Klasse nun überall vorhanden ist - und nicht nur lückenhaft ;-)

Oliver Hader wrote:

Hi Jürgen, nice to read from you here again :)

From an EventSourcing point of view (we don't have EventSourcing in the core) I totally get to point to check what has changed and only process/project those changes - e.g. trigger rendering of pages that were changed or warm-up their caches again.

Usually the meaning of "tstamp" was "modified by editor" which actually would not be the case when the sorting value was updated because some other record was inserted and sorting values had to be reprocessed.

I need to think a little bit about potential implications...

Alright then... I did not check in detail when tstamp is updated and when not... if it's updated in other places as well, I'm fine with completing the missing spots

Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/63962

• Jürgen, your changes have been pushed to to Gerrit at https://review.typo3.org/q/Ic7244cd3a829eca60c608de5caa09de95f98cf42 - could you please have a look?
• Benni, could you please check (or describe) the aspects you described above on sys_history?

Hi Oli,
i can't login at https://review.typo3.org. But nevertheless, the code looks good for me at https://review.typo3.org.

Best regards,
Jürgen

Oliver Hader wrote:

• Jürgen, your changes have been pushed to to Gerrit at https://review.typo3.org/q/Ic7244cd3a829eca60c608de5caa09de95f98cf42 - could you please have a look?
• Benni, could you please check (or describe) the aspects you described above on sys_history?

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/63961