Query History
Query History
DBeagle records recent query executions internally. Today that history is mainly used to power inline feedback in the editor rather than a standalone history browser.
The current history store keeps the last 50 execution entries.
What gets recorded
Each history entry captures:
| Field | Description |
|---|---|
| Connection | Which database connection was used |
| Document | Which file or scratch the query ran from |
| Selection | Whether the run used a text selection |
| Statements | Number of statements in that execution |
| Statement Types | The statement types DBeagle detected |
| Outcome | Success, cancelled, or failed |
| Timing | Start time, completion time, and total execution time when available |
| Row Count | Total rows materialized across statements |
| Error | Error message when the run fails |
Where you see it today
Current user-facing history surfaces include:
- Gutter annotations for recent statement runs
- Code lenses that let you jump back to the Results panel
- Result details such as query id, statement position, and rendered SQL
There is not yet a dedicated history explorer UI in the current release.
What it is useful for today
- Quick feedback on which statement last succeeded, failed, or was cancelled
- Fast access back to the DBeagle Results panel from the editor
- Future-facing groundwork for richer history features later
Retention behavior
The display is short and practical:
- New entries push older ones out once the
50entry limit is reached. - Clearing extension storage or resetting VS Code state removes the stored history.
Not shipped yet
- A full query history browser
- Search and filtering over past executions
- Re-running directly from a history list