Bug #79635

Updated by Thomas Hohn over 7 years ago

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 a new hook processDatamapAfterDatabaseOperations that can be used for to get 
 a coalescent the entries into one record. version and keeping processDatamap_afterDatabaseOperations for backwards