#100035DataHandler: Unnecessary database updates may result in timeout
Description
Scenario given:
- A content element of type “Image” with ~80 referenced images
- A shared hosting webspace with a 6-core CPU
- A remote database with unknown specs
Even without any changes, saving the content element always results in a server-side timeout.
Side note: Increasing the timeout is impossible without paying the hosting provider extra money.
I discovered that unnecessary database updates are done for each(!) referenced element as the DataHandler internally switches t3ver_stage to “0” to start a new editing workflow. However, this is done after DH checked whether field updates are necessary at all.