Datastore-specific guides
Redis And Valkey Workflows
Browse keys, inspect types, run console commands, and protect key operations.
Prerequisites
- Install the current DataPad++ desktop pre-release and open the workspace where you want to organize your connections and saved work.
- Have access to a datastore or database file you are authorized to inspect. Start read-only with a least-privileged account.
Quickstart
- 1
Start in the key browser
Redis and Valkey open with key browsing first so you can filter by pattern, type, TTL, memory, and length before reaching for raw commands.
Redis key browser. Key filters, type-aware value surfaces, TTL, and guarded key actions. Open full size - 2
Scan incrementally
Use Scan more and refresh controls to avoid assuming a full keyspace is loaded at once.
Key-value context actions. The read-only entry menu exposes copy and full-value inspection actions while mutation controls remain unavailable. Open full size - 3
Inspect by type
Strings, hashes, lists, sets, sorted sets, streams, JSON, TimeSeries, and supported module values should render through type-aware panels where available.
Security settings. Global safe mode explains how risky writes, inline edits, API and MCP requests, and read-only work are guarded. Open full size - 4
Use the console for precise commands
Switch to Redis console mode when you need command syntax, known-key hints, module hints, or direct read commands.
- 5
Guard live key changes
Edits, renames, TTL changes, deletes, stream updates, imports, and exports require concrete key identity and environment checks.
Task and control reference
The workbench keeps the active connection, environment, target scope, query mode, and panel state visible. Review that context before you run, edit, export, or administer anything.
Safety boundaries
Troubleshooting
| Symptom | What to check |
|---|---|
| A control is disabled | Read its disabled reason, then verify target scope, connection health, read-only mode, environment policy, and feature maturity. |
| The screen does not match this guide | Confirm the app version and platform, refresh the active tab, and check whether the feature is marked Experimental, Plan only, or Unavailable. |
| The operation produces no rows | Open Messages and History, verify the selected datastore scope, replace the sample object names with names from your datastore, and retry with a bounded read. |