Queries
Run SQL and Redis commands against a connection every tab names.
Statements you write run directly rather than being staged. Every query tab shows the connection it will run against.
SQL
The editor has syntax highlighting, bracket matching, indentation, find and replace, and completion for the schemas, tables, columns, and functions of the connected database.
A run covers the selection, the statement at the caret, or every statement in the editor. Statements run one at a time, and a failure ends the run instead of continuing into the statements that depended on it. Multiple results and command messages appear in order.
Results stream into a bounded grid and report the target connection, duration, fetched and affected rows, truncation, and final state. When a limit is what ended a result, the summary says so.
A failing statement moves the caret to the position the database reported and marks it. It never rewrites what you typed.
You can stop a running query. If it finishes before the cancellation reaches the database, Tablify reports it as completed rather than cancelled.
Redis commands
The command tab keeps a history, shows replies, and can cancel work in flight. Each command is classified by risk before it runs.
Saved statements
Unsaved editor text survives closing a tab, disconnecting, quitting, and crashing, bounded at 256 KiB per tab. Restoring it runs nothing.
Statements worth keeping can be saved, searched, renamed, duplicated, and grouped into folders. History holds the last 500 entries. A statement over 8 KiB is left out of history rather than stored cut short, because half a statement cannot be run again.