#111124Align LIMIT expectations of the Extbase conformance suite with CONTENT
Description
The conformance suite (#110797) marks “LIMIT is applied in SQL before the overlay drops rows” with a todo as an inconsistency. Core's CONTENT object behaves the same way: select.max@ limits in SQL before the language/workspace overlay drops rows, so fewer rows than the limit can be returned. As CONTENT is the core reference for record lists, the @todo is wrong.
The real deviation is the other direction: with respectSysLanguage enabled, Extbase excludes default rows without a visible translation in SQL and returns the full limit, while CONTENT returns fewer rows. The suite should pin that instead.
Reviews 1
Related issues 1
History 23
-
Alexander Schnitzler changed due date start date Follows #110797 <span data-processor="relativetime" data-value="2026-10-17T18:13:59+00:00" > 10/17/26, 18:13 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 96801 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-10-17T18:22:06+00:00" > 10/17/26, 18:22 </span> -
Alexander Schnitzler commented and changed status
Under ReviewRejected <span data-processor="relativetime" data-value="2026-10-20T11:19:25+00:00" > 10/20/26, 11:19 </span>
It treated “LIMIT is applied in SQL before the overlay drops rows“
as expected behaviour, because CONTENT’s select.max cuts the same
way. We concluded the opposite: the goal for Extbase is LIMIT after
the overlay, so fewer rows than the limit is a gap to close, not a
behaviour to pin.
The conformance suite on main reflects that: #96798 keeps the
“before overlay” case as a @todo and already contains the
respectSysLanguage limit test this change added.