TYPO3 v12 QueryResultPaginator does not rebind limit/offset after QueryResult materialization

Correct order of instantiation

The paginator must be created **with the raw Extbase Query object** *before* any method that materializes the QueryResult (e.g., execute(), toArray(), iteration, or count() on the result). When the paginator receives an unexecuted query it internally rebinds setLimit() and setOffset() just before the query is run.

Confirmed facts from the research brief

• Instantiating QueryResultPaginator with an unexecuted query causes the paginator to apply limit/offset to the underlying query before execution.
• Calling ->toArray(), iterating, or ->count() on the QueryResult materializes it and prevents the paginator from rebinding limit/offset.
• The paginator clones the query; further modifications to the original Query object after paginator creation do not affect the paginated query.

Steps to guarantee limit/offset are applied

1. Obtain the query from the repository: $query = $this->createQuery();
2. Optionally add any constraints (where, ordering, etc.) to $query.
3. Create the paginator **immediately**: $paginator = \TYPO3\CMS\Core\Pagination\QueryResultPaginator::create($query, $limit, $offset);
4. Retrieve the paginated result for rendering: $result = $paginator->getQueryResult();
5. Iterate over $result in the Fluid template or controller.

If you prefer to set limit/offset manually, do it on the query before creating the paginator:

$query->setLimit($limit)->setOffset($offset);
$paginator = \TYPO3\CMS\Core\Pagination\QueryResultPaginator::create($query);

Using a dedicated count query

For pagination controls you need the total number of rows. Obtain it **before** materializing the QueryResult:

• $total = $query->count(); executes a lightweight COUNT query and does not affect limit/offset rebinding.
• After getting $total, you can still create the paginator as shown above; the paginator will apply its own limit/offset.
• For very large tables where the COUNT is expensive, consider caching the count (e.g., using the Cache framework) or using an approximate count if exactness is not required.

Verification (safe, scoped)

1. Enable SQL logging in LocalConfiguration.php (set DEBUG or add a Doctrine SQL logger).
2. Run the repository method and check the log: the SELECT statement executed for the paginated query should contain LIMIT … OFFSET ….
3. Confirm that the number of rows returned matches $limit (or fewer for the last page) and that the pagination UI shows the correct total from the separate count query.