pub const MAX_LIST_LIMIT: i64 = 1000; // 1_000i64Expand description
Hard ceiling on the limit query parameter (REST) / RPC list-input
field every generated list route accepts, regardless of whether the
model is @@paged. Requests above this are rejected with a 400,
the same way negative limit/offset already are — see
handle_list_<plural>_dispatch in the generated code, shared
byte-for-byte between REST and RPC dispatch.
Without this, a caller can request an arbitrarily large limit and
force the generated handler to fetch (and, for @@paged models,
separately COUNT) an unbounded number of rows in one request — a
resource-exhaustion vector with no framework-level mitigation.
Chosen as a generous-but-real ceiling rather than a small one: it
should never trip on realistic paginated-UI or batch-export usage,
only on pathological/abusive requests.