Saved queries & history
Save PartiQL statements and revisit your per-table query history.
Tablyne keeps two running records of your PartiQL work: a history of statements you’ve run, captured automatically, and saved queries you name and keep on purpose.
Query history
Every time you run a PartiQL statement in SQL mode, Tablyne records it. Open the history menu next to the run button to revisit and reload past statements for the current table.
History is per table and ordered newest-first:
- Up to 25 statements are kept per table.
- An immediate duplicate (running the same statement twice in a row for the same table) isn’t recorded again, so the list stays useful.
- A global cap of 500 entries across all tables evicts the oldest when exceeded, so history can’t grow without bound.
Click any entry to load it back into the editor; from there you can tweak and run it again. Loading from history does not re-run the statement on its own — you still press ▶ run or Ctrl+Enter — which keeps SQL mode’s never auto-runs guarantee intact. You can also clear the history for a table when it gets noisy.
History is meant for the “what did I just run?” moment — quick recall during exploration. It’s cheap because it captures only the statement text and a timestamp, never results. For statements you want to keep around deliberately and find by name, save them instead.
Saved queries
The saved queries menu lets you give a statement a name and store it. Saved queries are scoped to a table, so when you’re on orders you see the queries you saved for orders.
| Field | Notes |
|---|---|
| Name | A label you choose, e.g. open orders this week |
| Table | The table the query belongs to |
| SQL | The PartiQL statement text |
To save the statement currently in the editor, open the menu and add it with a name. To reuse one, pick it from the list and it loads into the editor — then run it with ▶ run or Ctrl+Enter (loading a saved query does not auto-run it, consistent with SQL mode never running on its own). Remove a saved query when you no longer need it.
Where they’re stored
Both history and saved queries are persisted locally in the app (browser/local storage on your machine). They are:
- Per machine — they don’t sync across devices or team members.
- Local-only — nothing about your queries leaves your computer.
- Tied to the table name, so two tables with the same name in different accounts/regions share the same lists.
Because they’re local, history and saved queries survive across app restarts but won’t appear on a teammate’s machine. If you need to share a query with others, copy the statement text (or use a collection) rather than relying on the saved list.
Collections
For sharing or grouping a related set of requests — rather than a flat per-table list — Tablyne also has collections, accessible from the SQL toolbar. Collections are the right tool when you have a recurring workflow made of several statements (set up data, query it, clean up), or when you want to organize requests beyond a single table’s history. Running a collection’s request switches to SQL mode and loads the statement for you. See /docs/collections/.
Limitations to keep in mind
- History and saved queries are local and not synced — they live on the machine where you ran them.
- History capture and the editor cover PartiQL (SQL mode); the Busca condition builder is not recorded as history.
- Lists are keyed by table name only, so identically named tables across accounts/regions are not distinguished.