Project

General

Profile

Actions

Bug #89555

closed

Querying records in workspaces does not return all proper values due to "pid=-1" database

Added by Benni Mack about 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Workspaces
Start date:
2019-09-13
Due date:
2019-09-13
% Done:

100%

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

Description

Versioned records have "pid=-1" due to heavy legacy reasons before we had Doctrine DBAL and Restrictions, where one could accidentally query versioned records in their third party extension.

"pid=-1" has several drawbacks on versioned records:
- One could never query results properly by doing SQL queries on versioned records (as only equivalent live records were selected, and then overlaid)
- Unnecessary logic regarding moving and sorting due to versioned records

I propose to migrate to the proper "pid" of the live version, and look at "t3ver_oid" (live record) as all queries in the Core are already work based on this field.

An upgrade wizard then sets the "pid" field properly for all existing versions.


Related issues 7 (0 open7 closed)

Related to TYPO3 Core - Bug #91144: Copying records in pid 0 is not possible anymoreClosed2020-04-20

Actions
Related to TYPO3 Core - Bug #91851: Page module translation wizard shows duplicate records if in workspaceClosed2020-07-23

Actions
Related to TYPO3 Core - Bug #91943: Workspace preview shows correct items for sub menusClosed2020-08-06

Actions
Related to TYPO3 Core - Task #96279: Remove v9->v10 upgrade wizardsClosed2021-12-07

Actions
Related to TYPO3 Core - Task #98475: Avoid negative pid's in SQL schemaClosed2022-09-29

Actions
Follows TYPO3 Core - Bug #89122: Inconsistent evaluation of pid=-1 with workspace recordsClosedBenni Mack2019-09-112019-09-11

Actions
Precedes TYPO3 Core - Bug #91881: Massive load when deleting sys_workspace record on pid 0Closed2020-07-28

Actions
Actions

Also available in: Atom PDF