ZRANGE

Returns members in a sorted set within a range of indexes.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	ZRANGE
Catalog group	Sorted set commands
Upstream since	1.2.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

ZRANGE key start stop [BYSCORE | BYLEX] [REV] [LIMIT offset count]
  [WITHSCORES]

ffkv behavior and limits

Scores and lexicographic ranges are separate query modes. Do not rely on random-pop order; sorted-set storage remains RAM-resident in hybrid mode.

Source: README.md:275–295, 810–825; tests/bdd/features/sorted_sets.feature.

All requests share the 8 MiB framing/1,024-argument ingress limit; normal RESP replies have 64 MiB wire/logical budgets with bounded nesting/value counts. Management and Lua origins impose smaller budgets. These are not a process RSS cap. Catalog inclusion is not exhaustive option or wire-format parity. See limits and compatibility.

Upstream metadata

The following fields come from the pinned Redis metadata, not measured ffkv performance or an assertion that ffkv enforces every upstream flag. Running COMMAND INFO/COMMAND DOCS describe the current engine.

Upstream Redis complexity: O(log(N)+M) with N being the number of elements in the sorted set and M the number of elements returned.

Upstream arity: -4 (includes the command name; a negative number is a minimum).

Command flags: READONLY.

ACL categories: SORTEDSET.

Argument structure

Argument	Type	Constraints / metadata
key	key	key_spec_index: 0
start	string	Required
stop	string	Required
sortby	oneof	optional; since: 6.2.0
↳ byscore	pure-token	token: BYSCORE
↳ bylex	pure-token	token: BYLEX
rev	pure-token	optional; token: REV; since: 6.2.0
limit	block	optional; token: LIMIT; since: 6.2.0
↳ offset	integer	Required
↳ count	integer	Required
withscores	pure-token	optional; token: WITHSCORES

Key specifications

Upstream key discovery descriptors (indexes are relative to the full command vector):

[
  {
    "flags": [
      "RO",
      "ACCESS"
    ],
    "begin_search": {
      "index": {
        "pos": 1
      }
    },
    "find_keys": {
      "range": {
        "lastkey": 0,
        "step": 1,
        "limit": 0
      }
    }
  }
]

Additional pinned upstream metadata

{
  "group": "sorted_set",
  "since": "1.2.0",
  "history": [
    [
      "6.2.0",
      "Added the `REV`, `BYSCORE`, `BYLEX` and `LIMIT` options."
    ]
  ]
}

Metadata source · Local snapshot: src/command_metadata.json, key zrange.

BDD coverage and source examples

These are source observations, not a test run performed by this documentation build. A tag identifies scenario intent; an extracted vector identifies a command invocation, which may intentionally produce an error. Scenarios may require setup, multiple connections, persistence, cluster nodes or native-module fixtures.

• ZADD applies conditional changes sequentially and preserves expiry — tests/bdd/features/sorted_sets.feature:4; invocation observed.
• Modern ranges support score and lex modes with reverse pagination — tests/bdd/features/sorted_sets.feature:209; command tag and invocation observed.
• Rank removal resolves negative indexes before changing the indexes — tests/bdd/features/sorted_sets.feature:385; invocation observed.
• Score removal leaves exclusive lower-bound members intact — tests/bdd/features/sorted_sets.feature:409; invocation observed.
• Lex removal preserves scores and deletes the last-member key — tests/bdd/features/sorted_sets.feature:433; invocation observed.
• Difference store can overwrite its source and clears destination TTL — tests/bdd/features/sorted_sets.feature:609; invocation observed.
• Union store counts weighted memberships instead of original scores — tests/bdd/features/sorted_sets.feature:705; invocation observed.
• Intersection store resolves source aliasing and normalizes infinity NaN — tests/bdd/features/sorted_sets.feature:729; invocation observed.
• Range store resolves source before overwrite and preserves original scores — tests/bdd/features/sorted_sets.feature:753; invocation observed.
• Blocking maximum pop wakes and respects reverse tied member order — tests/bdd/features/sorted_sets.feature:861; invocation observed.
• RESP3 scored ranges and pop replies use nested native doubles — tests/bdd/features/sorted_sets.feature:917; command tag and invocation observed.
• Malformed range bounds and limits leave data unchanged — tests/bdd/features/sorted_sets.feature:1035; command tag and invocation observed.
• Resolved scores stores and removals survive crash recovery — tests/bdd/features/sorted_sets.feature:1126; invocation observed.
• Lex bounds compare binary bytes and store the selected scored members — tests/bdd/features/sorted_sets.feature:1236; invocation observed.
• Intersection preserves raw later infinity products in every aggregate and stored score (Scenario Outline) — tests/bdd/features/sorted_sets.feature:1318; invocation observed.

Extracted command vectors

The following JSON arrays are the test harness’s argument vectors, not shell commands. Numeric arguments are converted by the harness; objects of the form {"base64":"…"} represent decoded binary bytes, not a literal JSON command argument. Preserve scenario setup and connection ordering. See the CLI guide for shell quoting and binary stdin. No reply is invented or inferred.

Rank removal resolves negative indexes before changing the indexes — tests/bdd/features/sorted_sets.feature:399 (I execute:)

[
  "ZRANGE",
  "ranked",
  "0",
  "-1"
]

Next source assertion: the reply equals:

["a","b"]

Modern ranges support score and lex modes with reverse pagination — tests/bdd/features/sorted_sets.feature:223 (I execute:)

[
  "ZRANGE",
  "ranked",
  "-2",
  "-1"
]

Next source assertion: the reply equals:

["c","d"]

Lex removal preserves scores and deletes the last-member key — tests/bdd/features/sorted_sets.feature:447 (I execute:)

[
  "ZRANGE",
  "letters",
  "0",
  "-1"
]

Next source assertion: the reply equals:

["a","c"]