Project

General

Profile

Actions

Bug #79635

closed

Coalescence calls to processDatamap_afterDatabaseOperations

Added by Thomas Hohn about 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
DataHandler aka TCEmain
Target version:
Start date:
2017-02-06
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Due to a bug in the Datahandler - extra expensive processing of the hook
processDatamap_afterDatabaseOperations can occur for remapping calls.

Current situation in vanilla TYPO3 installation:
Create page with 1 tt_content element. Copy that page.
This triggers 1 call to processDatamap_afterDatabaseOperations for the page - but also 3 calls to
processDatamap_afterDatabaseOperations for the tt_content element.

It is possible to coalescent calls to processDatamap_afterDatabaseOperations
into one pr. table instead of one pr.
remapstack entry in processRemapStack

It would be better only to issue 1 call for the tt_content element with the "combined" processing array
since each subscriber would need to filter the other 2 calls if only the "signal" that a change
on the table has occurred.

The solution is to add coalescent the entries into one record.


Files

processRemapStack.php (7.3 KB) processRemapStack.php Thomas Hohn, 2017-03-09 13:15
processRemapStack.log (14.7 KB) processRemapStack.log Thomas Hohn, 2017-03-09 13:15
Actions

Also available in: Atom PDF