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.