Why GETRANGE and SETRANGE in Redis? - Purpose & Use Cases

The Big Idea

What if you could fix or read just a tiny part of your data instantly, without touching the rest?

The Scenario

Imagine you have a long text saved in a file or a note, and you want to read or change just a small part of it without opening or rewriting the whole thing.

The Problem

Manually opening the entire file or string, reading it all, then rewriting it just to change a few characters is slow and can cause mistakes. It wastes time and can break the data if done wrong.

The Solution

GETRANGE and SETRANGE let you quickly read or update only the part you want inside a stored string, without touching the rest. This saves time and keeps your data safe.

Before vs After

✗ Before

full_text = redis.get('key')
new_text = full_text[:5] + 'hello' + full_text[10:]
redis.set('key', new_text)

✓ After

redis.setrange('key', 5, 'hello')
partial_text = redis.getrange('key', 5, 9)

What It Enables

You can efficiently access or update parts of stored strings instantly, making your app faster and more reliable.

Real Life Example

Think of a chat app where you want to update just a word in a saved message or read a snippet without loading the entire conversation.

Key Takeaways

Manual string edits are slow and risky.

GETRANGE and SETRANGE target only needed parts.

This makes data handling faster and safer.

Practice

1. What does the Redis command GETRANGE key 0 4 do?

easy

A. Returns the substring of the value stored at key from index 0 to 4 inclusive.

B. Deletes the first 5 characters of the string stored at key.

C. Replaces the first 5 characters of the string stored at key with zeros.

D. Returns the length of the string stored at key.

Solution

1. Step 1: Understand GETRANGE parameters

   The command GETRANGE key start end returns the substring from the start index to the end index inclusive.

2. Step 2: Apply to given indices

   With start=0 and end=4, it returns characters at positions 0,1,2,3,4 from the string stored at key.

3. Final Answer:

   Returns substring from index 0 to 4 inclusive -> Option A

4. Quick Check:

   GETRANGE extracts substring = A [OK]

Hint: GETRANGE extracts substring by start and end indexes [OK]

Common Mistakes:

• Thinking GETRANGE deletes or modifies the string
• Confusing GETRANGE with SETRANGE
• Assuming end index is exclusive

2. Which of the following is the correct syntax to replace part of a string value in Redis using SETRANGE?

easy

A. SETRANGE key value offset

B. SETRANGE key offset value

C. SET key offset value

D. GETRANGE key offset value

Solution

1. Step 1: Recall SETRANGE syntax

   The correct syntax is SETRANGE key offset value, where offset is the start position to replace and value is the new substring.

2. Step 2: Check options

   Only SETRANGE key offset value matches this syntax exactly.

3. Final Answer:

   SETRANGE key offset value -> Option B

4. Quick Check:

   Correct SETRANGE syntax = A [OK]

Hint: Remember SETRANGE order: key, offset, then value [OK]

Common Mistakes:

• Swapping offset and value positions
• Using GETRANGE instead of SETRANGE
• Using SET instead of SETRANGE

3. Given the Redis string value at key mykey is "HelloWorld", what will be the result of GETRANGE mykey 5 7?

medium

A. "World"

B. "Hello"

C. "loW"

D. "Wor"

Solution

1. Step 1: Identify substring indices

   The string is "HelloWorld" with indices: H(0), e(1), l(2), l(3), o(4), W(5), o(6), r(7), l(8), d(9).

2. Step 2: Extract substring from index 5 to 7

   Characters at 5,6,7 are 'W', 'o', 'r', so the substring is "Wor".

3. Final Answer:

   "Wor" -> Option D

4. Quick Check:

   GETRANGE returns substring = B [OK]

Hint: Count string indexes from 0 to get substring [OK]

Common Mistakes:

• Counting indexes starting at 1
• Including characters outside the range
• Confusing GETRANGE with SETRANGE

4. You run SETRANGE mykey 3 "abc" on a Redis string "abcdef". The result is unexpected. What is the likely mistake?

medium

A. Using quotes around the substring value in the command.

B. Offset 3 is out of range for the string length.

C. SETRANGE cannot modify existing strings.

D. The key mykey does not exist.

Solution

1. Step 1: Understand SETRANGE usage

   SETRANGE expects the substring value without quotes; quotes are interpreted literally.

2. Step 2: Identify the mistake

   Using quotes like "abc" inserts the quotes as characters, causing unexpected results.

3. Final Answer:

   Using quotes around substring causes wrong replacement -> Option A

4. Quick Check:

   Quotes in SETRANGE value cause errors = C [OK]

Hint: Do not include quotes around substring in SETRANGE [OK]

Common Mistakes:

• Including quotes around substring value
• Assuming offset must be within string length
• Thinking SETRANGE creates new keys automatically

5. If the Redis key text holds the string "abcdefghij", what will be the final string after executing SETRANGE text 5 "XYZ" followed by GETRANGE text 3 7?

hard

A. "defgh"

B. "fghij"

C. "deXYZ"

D. "defXY"

Solution

1. Step 1: Apply SETRANGE at offset 5

   Original string: "abcdefghij". SETRANGE replaces characters at positions 5,6,7 with "XYZ". Positions: a(0), b(1), c(2), d(3), e(4), f(5), g(6), h(7), i(8), j(9). After replacement: "abcdeXYZij".

2. Step 2: Apply GETRANGE from 3 to 7

   Characters at positions 3 to 7 are: d(3), e(4), X(5), Y(6), Z(7). So substring is "deXYZ".

3. Final Answer:

   "deXYZ" -> Option C

4. Quick Check:

   SETRANGE modifies substring, GETRANGE extracts it = D [OK]

Hint: Apply SETRANGE first, then GETRANGE on updated string [OK]

Common Mistakes:

• Not updating string before GETRANGE
• Miscounting offset positions
• Assuming GETRANGE returns original string