At what level in a three-tier architecture should pagination, filtering and sorting be?

Question

ASP.NET

Where should I place pagination, sorting and filtering.
All this should be done by the data layer (repository)?

Answer 1

of course, because the repository must know how to compose the skl (or what parameters to pass to the orm so that it generates the desired request).
you can go from the opposite - if the repository does not know anything about pagination / filtering, then you will need to get all the data from the database each time so that you can then select only those that need to be displayed. looks gross, doesn't it?)