Bug #91881
closed
Massive load when deleting sys_workspace record on pid 0
Added by Christian Kuhn about 4 years ago.
Updated almost 4 years ago.
Description
This is a regression introduced by #89555 in v10 & master.
Reproduce:
- Create a sys_workspace record on pid 0
- Delete this sys_workspace record on pid 0
-> The database throws a massive party with all live records of all tables as guests :)
Goal:
When deleting a sys_workspace record, all records of this workspace should be deleted (soft/hard delete, depending on table TCA).
Issue:
With #89555 the restrictions of the underlying query that should find and delete all records of this workspace has been changed to also include all live records of all tables. Luckily, this does not lead to delete hazard since a check at a later point in version_clearWSID() prevents live records from being deleted within workspaces. That check however creates a log entry for each live invalid party guest ... and it happily tells the user about each one with a notice in the top right corner. That corner is too small for many thousands guests ;)
Fix:
Add a proper database restriction again. Support that with some functional test to verify correct rows are deleted.
- Related to Bug #69310: Attempt to reset workspace failed added
- Related to Bug #61719: Warnings on flushing whole workspace with localizations added
- Due date set to 2019-09-12
- Start date changed from 2020-07-28 to 2019-09-12
- Follows Bug #89122: Inconsistent evaluation of pid=-1 with workspace records added
- Follows deleted (Bug #89122: Inconsistent evaluation of pid=-1 with workspace records)
- Precedes Bug #89555: Querying records in workspaces does not return all proper values due to "pid=-1" database added
- Precedes deleted (Bug #89555: Querying records in workspaces does not return all proper values due to "pid=-1" database)
- Due date changed from 2019-09-12 to 2019-09-16
- Start date changed from 2019-09-12 to 2019-09-16
- Follows Bug #89555: Querying records in workspaces does not return all proper values due to "pid=-1" database added
- Subject changed from Massive db load when deleting sys_workspace record on pid 0 to Massive load when deleting sys_workspace record on pid 0
- Description updated (diff)
- Due date deleted (
2019-09-16)
- Priority changed from Should have to Must have
- Start date changed from 2019-09-16 to 2020-07-28
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF