#57169Invalid relations of MM records in workspaces
Description
The basic problem with MM (ManyToMany) relations in workspaces is, that the intermediate table (MM table) does not have any information about actually being a reference in a particular workspace – there is no “t3ver_wsid” field. Thus, the meaning of a relation needs to be determined from the entities on both sides of the relation. The following is possible:
- both sides of the relation are live -> valid in live only
- exactly one side of the relation is versioned -> valid in a workspace only
- both sides of the relation are versioned -> valid in a workspace only
The difficulties now start with versioning one side first and after some time the other side – thus the relation with exactly one version and one live entity needs to be turned into an entry pointing to both versions.
Reviews 6
- main 81166[BUGFIX] Fix performance issue when resolving Extbase relations in workspaces
- 13.4 87627[BUGFIX] Fix performance issue when resolving Extbase relations in workspaces
- 12.4 87626[BUGFIX] Fix performance issue when resolving Extbase relations in workspaces
- 11.5 72268[BUGFIX] Better sys_refindex with workspace mm
- main 72250[BUGFIX] Better sys_refindex with workspace mm
- main 28624[BUGFIX] Invalid relations of MM records in workspaces
Related issues 5
- Bug #57291RelationHandler->purgeItemArray() should use isTableWorkspaceEnabled check
- Bug #57303DB Error when editing a record without versioning
- Bug #83582Records with pid=-1 are shown in backend in field of type "group" using a MM relation
- Bug #89456Translations of IRRE Extbase Records in Workspaces not saved
- Bug #99244DataMapper uses a lot of memory when retrieving MM-relations in workspaces