Bug #47354
closedMake DBgetDelete() update tstamp on delete by update
100%
Description
In ContentObjectRenderer::DBgetDelete() it is possible that TCA for a table instructs TYPO3 to not really delete the row but only mark it as deleted. If that happens an "update" is performed - and thus the tstamp (if present) should be updated as well to be able to see which rows were (recently) modified/deleted.
This is the case since "forever" (at least 4.5, but surely longer). Thus if we decide to change this behavious, we should maybe also do so for master or maybe in 6.1 but not too much further down. It's imho not a "hard" behaviour-breaking change since until now you could not rely on tstamp being updated - and now the row will be visible as recently changed. But it's a behaviour-change after all.
Updated by Gerrit Code Review over 11 years ago
- Status changed from New to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20024
Updated by Gerrit Code Review over 11 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20024
Updated by Gerrit Code Review over 11 years ago
Patch set 1 for branch TYPO3_6-1 has been pushed to the review server.
It is available at https://review.typo3.org/22286
Updated by Stefan Neufeind over 11 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 1eaeab881d5122d9f3cb4a799c0bdca9cb7e42bd.