Contao List Module SQL Limit Behavior

List Module SQL Data Source Query Behavior

0 reputation · 09 Feb 2022, 21:12 UTC

99.9K views0

Contao List Module Pagination

The list module utilizes a generic SQL data source configuration.

Query Execution Constraint

When this data source is selected, the system loads the entire underlying database table into PHP memory.

What is the documented behavior regarding the application of the SQL LIMIT clause during pagination for Contao versions 4.6 through 5.0?

Does the pagination loop result in N+1 queries when using the SQL data source?
Is there a documented configuration override to enforce SQL limiting at this stage?

4,078 following

0 answers

Keep exploring this topic

Contao Model::findBy() count query overhead when paginating large datasets

Contao's Model::findBy() runs a COUNT(*) query whenever limit is set, adding overhead on large tables. No built-in option suppresses this count or enables keyset pagination.

Cassandra 4.0 PagingState token reuse after session closure remains undefined

Cassandra 4.0’s PagingState token lacks a documented lifecycle rule for reuse after session closure, leaving applications uncertain about safe pagination resumption.

Godot SceneTree Group Queries Lack Pagination and Result Limits

Godot's get_nodes_in_group returns a full array with no pagination, causing frame hitches on large groups. Workarounds require custom registries with manual tree notifications. What are the practical thresholds and roadmap plans?

Global file lock contention causing latency spikes under concurrent writes in Contao

Assess how the global file lock influences request latency when multiple concurrent requests write to the same Contao table, given the lack of per-request transaction isolation and the risk of SQLSTATE[40001] deadlocks.

List Module SQL Data Source Query Behavior

Contao List Module Pagination

Query Execution Constraint

0 answers

Your perspective belongs here.

0 question comments