Phalcon Paginator QueryBuilder adapter transition from v3 to v4

Namespace and Adapter Compatibility

Phalcon 4 introduced significant architectural changes to its namespace structure, moving away from the tighter coupling found in version 3. This shift affects how the Phalcon\Paginator and its associated adapters, such as the QueryBuilder adapter, are instantiated and utilized within the ORM.

Offset Performance Constraints

When implementing pagination for large datasets, the QueryBuilder adapter relies on database-level OFFSET and LIMIT clauses. As the page index increases, the performance of these queries typically degrades regardless of the framework's C-extension efficiency, creating a bottleneck during the transition to higher page numbers.

There is uncertainty regarding the most efficient way to maintain result count accuracy when utilizing complex joins within the updated Phalcon 4 Paginator architecture without triggering full table scans.

• Does the Phalcon 4 QueryBuilder adapter handle join-based result counts differently than the v3 implementation?
• What is the recommended configuration to mitigate offset latency for deep pagination in version 4?