VIEW.CREATE
Declare a composed view over indexes with an ORDER BY (catalog mutation, sidecar-persisted).
VIEW.CREATE name QUERY tree ORDER BY index [DESC] [MODE virtual|materialized] [TOPK k] [VIA template] (tree = '( AND|OR|DIFF sub sub )' | 'index RANGE min max' | 'index EQ value')Complexity
O(tree size) at the call. A materialized view builds lazily on the next tick (a full eval_tree plus an O(M log M) sort); a virtual view builds nothing, ever
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. A view is neither a stored query nor a join — it is a named composition tree over declared indexes that stores membership and order only, never field values
See also
VIEW.DROPVIEW.EXPLAINVIEW.LISTVIEW.QUERYVIEW.REBUILDVIEW.VERIFY