SQLlyQuery History
✓ functionalSearch the local execution log, keep pinned snippets, and send any statement back to the editor.
A browser over the local execution log, split into Pinned and
Recent. Each row shows a one-line SQL preview (or the pin's name, if
you gave it one) with its server, database, when it ran, whether it succeeded, how long
it took, how many times it has run, and rows affected. The search box takes plain text
or structured filters - server:prod db:sales outcome:failed min:1s - plus
after:/before: dates and tag:.
- Open in New Tab scripts the full statement back to the editor for review; Run re-runs it in one step - a deliberate exception to the review pause, since it is SQL you already ran.
- Pins are saved queries - a pinned entry gains inline name, description, and tag editors, survives retention pruning, and can be exported and imported as JSON or written into the SQL Library as
.sqlfiles. - Analyze with AI hands the entry - or the last five visible ones - to the AI panel, and entries that stored rollback SQL offer Copy rollback SQL.
The history lives in a local file, like the rest of your SQLly setup - it is yours to keep, search, and back up. The list pages through the log in chunks, and the footer counts what retention has pruned.