Prefer ZRANGE with BYLEX in new code: ZRANGE <key> <min> <max> BYLEX [LIMIT <offset> <count>].
Use ZRANGEBYLEX to list the members of a sorted set that fall in a lexicographic range.
Bounds are written [member for inclusive and (member for exclusive, with - and + standing for the lowest and highest possible members. LIMIT <offset> <count> pages through the result.
The ordering used here is the byte order of member names, which is only meaningful when every member has the same score. Giving all members score 0 turns a sorted set into a sorted string index, which is how prefix lookups and autocomplete are built on top of it.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<min> | Yes | No | Lexicographic minimum: -, +, [member (inclusive), or (member (exclusive). |
<max> | Yes | No | Lexicographic maximum: -, +, [member (inclusive), or (member (exclusive). |
LIMIT <offset> <count> | No | No | Skip <offset> matches and return at most <count>; a <count> of -1 returns all remaining. |
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Array of bulk-string members |
| RESP3 | Array of bulk-string members |
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.
Redis CLI
@upstash/redis
This command is not supported yet in @upstash/redis.