VIEW.QUERY
Page through a view's ordered members, optionally hydrating fields via the VIA template.
VIEW.QUERY name [LIMIT n] [CURSOR c] [FIELDS field ...]Complexity
virtual: O(log N_order + candidates * leaves) — it streams the ORDER index and probes membership per candidate, stopping at the limit, so it never materialises the member set. materialized: O(log M + limit). Adding FIELDS with VIA costs a SECOND fan-out to hydrate the rows
Complexity and compatibility are read out of kevy's implementation, not copied from Redis's reference. Several genuinely differ.
Redis compatibility
kevy only
kevy has this; Redis does not. no Redis analogue. Absent by construction: no joins, no predicates at the view layer, no projection from the view itself, no HAVING, no aggregation
See also
VIEW.CREATEVIEW.DROPVIEW.EXPLAINVIEW.LISTVIEW.REBUILDVIEW.VERIFY