Performance Issue: Inefficient Slicing of Connection Queries

Performance Issue: Inefficient Slicing of Connection Queries

Currently, when performing a connection query with arguments like first: 20, after: some_token, the system retrieves the entire dataset from the database and then applies slicing in-memory. This approach becomes increasingly inefficient as the size of the database grows.

It would be highly beneficial to support slicing directly at the database level to improve performance and reduce unnecessary data processing.

Suggested Improvement:
Implement database-level pagination to handle first, after, etc., during the query execution phase, rather than after data retrieval.

The issue names no files, tests, or entry points. Start by tracing how connection queries retrieve data and apply first/after slicing, then inspect the SQLAlchemy query construction path. Done means pagination arguments are applied at the database level without retrieving the entire dataset, with performance behavior verified for large result sets.

Escrita pelo modelo de indexação a partir do texto da issue.