Sort and page

Sort

pawabase.from("posts").order("created_at", "desc");
pawabase.from("posts").order("pinned", "desc").order("created_at", "desc");    // then by

pb.from_("posts").order("created_at", "desc")
pb.from_("posts").order("pinned", "desc").order("created_at", "desc")

Each order after the first breaks ties in the earlier ones. Ascending is the default. Without any order, the order is not guaranteed; always sort lists you show.

Page size and number

const page2 = await pawabase.from("posts").order("created_at", "desc").perPage(25).page(2);
page2.page;       // 2
page2.per_page;   // 25
page2.total;      // matching records, or null

page2 = pb.from_("posts").order("created_at", "desc").per_page(25).page(2).execute()
page2.page, page2.per_page, page2.total

Pages count from 1. The default size is 20; the server caps it at 200. limit(n) asks for at most n records.

Turn paging off

Lists are paged by default. When you want every match in one response (a short dropdown, a small lookup table), ask for it.

const result = await pawabase.from("categories").order("name").paginate(false);
result.data;      // every match
result.page;      // null
result.per_page;  // null
result.total;     // how many came back

result = pb.from_("categories").order("name").paginate(False).execute()
result.data, result.total   # result.page and result.per_page are None

curl "$URL/rest/v1/categories?paginate=false&sort=name" -H "apikey: $KEY"

The response keeps its shape: { "data": [...], "page": null, "per_page": null, "total": 42 }. page and per_page are ignored when paginate=false. One response holds at most 5000 records. If more match, the server answers 400 rather than quietly cutting the list short, so narrow it with filters or go back to paging. For large tables, walk through everything instead.

Load more

Keep the page number and add results as it grows. Stop when a page comes back short; don’t rely on total, which can be null.

async function loadMore(state: { page: number; rows: Post[]; done: boolean }) {
  const next = await pawabase.from("posts").order("created_at", "desc").perPage(20).page(state.page + 1);
  return {
    page: state.page + 1,
    rows: [...state.rows, ...(next.data as Post[])],
    done: next.data.length < 20,
  };
}

Page controls (when `total` is a number)

const pages = page.total == null ? null : Math.ceil(page.total / page.per_page);
// Show "Page 3 of 12" only when `pages` is a number; otherwise show Previous / Next.

Walk through everything

For exports and background work, iterate instead of loading one huge page:

for await (const page of pawabase.from("orders").eq("status", "paid").pages({ pageSize: 100 })) {
  for (const order of page.data) process(order);
}

const all = await pawabase.from("orders").eq("status", "paid").all({ pageSize: 100, maxRecords: 5000, stopAfterEmptyPages: 1 });

for page in pb.from_("orders").eq("status", "paid").pages(page_size=100):
    for order in page:
        process(order)

for order in pb.from_("orders").eq("status", "paid").iterate(page_size=100):
    process(order)

everything = pb.from_("orders").eq("status", "paid").all(page_size=100, max_records=5000)

Option	Meaning
`pageSize`	Rows per request. Default 100; the server maximum is 200
`maxRecords`	Stop after this many rows. A safety stop
`stopAfterEmptyPages`	When the server can’t count (`total` is `null`), a short or empty page doesn’t mean the end. Stop after this many empty pages in a row (default 1)

pages yields one page at a time, so memory stays flat.

Stable pages

If records arrive while someone is paging, items shift between pages. For feeds:

Sort by something steady (created_at, then id).
Prefer “load newer” with a filter (gt("created_at", lastSeen)) over page numbers.
Let realtime add new records at the top instead of re-reading page 1.

Keyset-style paging

For very large tables, “give me 20 older than this” is faster than deep page numbers, because the database doesn’t count skipped rows:

async function olderThan(cursor: string) {
  return pawabase.from("events").lt("created_at", cursor).order("created_at", "desc").limit(50);
}

Pass the last item’s created_at as the next cursor. Make sure created_at is indexed.

Read records

All the ways to read.

Live records

New rows as they arrive.

Getting started

Define your data

Change safely

Read and write

Protect and shape

Studio tools

Build well

Sort

Page size and number

Turn paging off

Load more

Page controls (when `total` is a number)

Walk through everything

Stable pages

Keyset-style paging

Read records

Live records

​Sort

​Page size and number

​Turn paging off

​Load more

​Page controls (when total is a number)

​Walk through everything

​Stable pages

​Keyset-style paging

Read records

Live records

Sort

Page size and number

Turn paging off

Load more

Page controls (when `total` is a number)

Walk through everything

Stable pages

Keyset-style paging