Ordering and Paging

Use OrderBy(...) and OrderByDescending(...) with typed member selectors or CLR property-name strings.

var users = connection
    .UseDb4Net(Db4NetOptions.SqlServer)
    .SelectFrom<User>()
    .OrderBy(u => u.Name)
    .OrderByDescending(u => u.Id)
    .Query();

Limit and Offset

Offset(...) must be paired with Limit(...).

var users = db.SelectFrom<User>()
    .OrderBy(u => u.Id)
    .Limit(20)
    .Offset(40)
    .Query();

Page

Page(pageNumber, pageSize) uses one-based page numbers.

var page = db.SelectFrom<User>()
    .OrderBy(u => u.Id)
    .Page(pageNumber: 2, pageSize: 20)
    .Query();

Query Page With Total Count

Use QueryPage(pageNumber, pageSize) when the caller needs both the current page and the total count of rows matching the same filters.

var page = await db.SelectFrom<User>()
    .Where(u => u.Name, Op.Like, "A%")
    .OrderBy(u => u.Id)
    .QueryPageAsync(pageNumber: 2, pageSize: 20);

var users = page.Items;
var totalCount = page.TotalCount;
var totalPages = page.TotalPages;

QueryPage(...) executes a count query and a paged row query internally. It applies paging itself; do not call Limit(...), Offset(...), or Page(...) before QueryPage(...).

Db4Net renders paging through the configured dialect:

• SQL Server: OFFSET ... ROWS FETCH NEXT ... ROWS ONLY
• SQLite: LIMIT ... OFFSET ...
• PostgreSQL: LIMIT ... OFFSET ...
• MySQL: LIMIT ... OFFSET ...

SQL Server paging requires at least one OrderBy(...) because OFFSET / FETCH is invalid without ORDER BY. Stable ordering is recommended for every dialect when paging.