Server Transcript
View statements sent on this connection, including the ones Querious sent for you.
The Server Transcript lists the most recently executed queries: ones you typed in the Query view, ones produced by editing a row, and ones Querious ran on its own to populate its views.


The List #
| Column | What it shows |
|---|---|
| Time | When the statement was sent. |
| Duration | Approximately how long it took. |
| Query | The statement, up to five lines. Select a query to see all of it in a more detailed view. |
Filtering #
Use the Show: scope bar above the transcript list to cut through the noise. In a busy session, the queries that Querious runs to gather information will vastly outnumber your own hand-executed queries, so you'll likely want to filter to find what you're looking for.
Filter the list with the scope bar above it:
| Filter | Shows |
|---|---|
| All | Everything sent over the connection. |
| User | Queries you wrote and in the Query view. |
| Fetches | Queries with no effect on data or structure, such as SELECT and SHOW. Querious ran these to read information for its views. |
| Actions | Queries such as FLUSH, LOCK, and SET, that act on the server without changing data. |
| Changes | Queries that can modify data or structure, such as INSERT, ALTER, CREATE, and DELETE. |
The search field matches statement text. Clear empties the history. It lives only in memory, so closing the tab or disconnecting discards it, and it's never written to disk.
Recipes #
To see exactly what an edit did
-
Make the change, such as editing a row in the Content view or altering a column in Table Columns.
-
Open Server Transcript and set Show: to Changes.
-
The top entry is what Querious sent. Click it to read it in full, and copy it to reuse in a migration.
To recover a query you ran and lost
-
Set Show: to User and search for a table name or keyword you remember.
-
Click the entry and copy it back into the Query view. If you'll want it again, save it. See Saved Queries.
To find the query behind a view
-
Set Show: to Fetches.
-
Switch to the view you're curious about and come back.
-
The new entries are what that view needed. When a view is slow to appear, Duration usually points at the expensive one.