Issue Bug Resolved

#110663GreedyCacheBackend is too greedy

Garvin Hicking 09/09/26, 12:26 updated 11/11/26, 13:55

Description

The cache resolving with pointers in GreedyCacheBackend only works well in a situation where all records to be looked up are within the same pid.

However, “Relations” (in contrast to “Collections”) for select/group scenarios may reference records from different PIDs. In these cases, the getRowsFromCache() method will return wrong results for a case where lookups intersect on a single UID. Then the rows of only one PID are returned, and are missing the pointer results from records in a different PID.

This is problematic for an extension like Content-Blocks where plugins for “teaser lists” are created to point to different pages, and return wrong results.

See https://typo3.slack.com/archives/C8Z2UM50Q/p1788877540991639 for more discussion.

Two approaches so far:

- Restrict the special caching to “Collections” only. Make “Relations” not utilize this optimized caching
- Generally restrict the optimized caching to PIDs

Reviews 3

History 38

  1. Gerrit Code Review pushed patch set 2 for main to change 95730 status Accepted Under Review <span data-processor="relativetime" data-value="2026-09-09T12:27:02+00:00" > 09/09/26, 12:27 </span>

  2. Garvin Hicking commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-11T13:55:11+00:00" > 11/11/26, 13:55 </span>

    Applied in changeset commit:1e12da3e02fd4eb2c31c1180abddddeef72531e1.