Query history, saved queries and export
The Console for PostgreSQL, MySQL, MongoDB, ClickHouse, Cassandra, Qdrant, OpenSearch, SQLite and the Redis family includes a local query library. History and saved queries survive app restarts.
History
Open History to see commands run on the current connection, with their time, duration, row count and success or error status. Search the text and click an entry to load it into the editor. Loading an entry does not execute it.
The app keeps the most recent 500 history entries across connections. Clear this history removes entries for the current connection. Existing console history is imported when you first open the console after upgrading.
Saved queries
- Enter a query and choose Save query.
- Give it a name.
- Leave it attached to this connection, or select Available on all … connections to reuse it on connections with the same engine.
- Open Saved to search, load, edit or delete it.
A saved query is still checked by the connection's current Safe Mode when you run it.
Export results
Use CSV or JSON beside a SQL, CQL, Qdrant or OpenSearch result table, or JSON for Redis replies and MongoDB documents. Files are written to your system Downloads folder under Recern, with a unique file name. Choose Saved in Downloads/Recern to reveal the file in your file manager.
Exports contain the displayed results, not a full database dump. SQL consoles show up to 1,000 rows per statement. If a result is truncated, the console says so; narrow the query or use a limit and pagination to retrieve another portion. SQL values are exported as the strings displayed by the console, with SQL NULL preserved as JSON null.
MongoDB exports Extended JSON to preserve BSON types, including ObjectId, dates and large integers. Document browsing shows 50 documents per page; the JSON console defaults to 100 and caps results at 1,000 documents. ClickHouse uses the SQL result exporter and also enforces memory, response-size and execution-time limits.
Cassandra uses the same table exporter and keeps large integers exact as strings. Qdrant also exports displayed table cells as strings, including numeric point IDs; payloads and vectors appear as JSON text in their cells. Scroll offsets are shown separately as exact JSON values for the next request. These exports are not full collection backups or vector migration files. See Cassandra and Qdrant for operation and size limits.
OpenSearch exports the displayed table only. Search results have at most 1,000 documents and an 8 MiB response cap; manual document pages contain 50 documents. Table cells and IDs preserve their displayed string values, with document fields encoded as JSON text where applicable. Exported pages are not an index backup. See OpenSearch.
Microsoft SQL Server exports the displayed bounded results: at most 1,000 rows, 128 columns and 8 MiB. Bigint and decimal values remain exact strings; duplicate column names, Unicode and nulls are preserved. TEXTSIZE can truncate supported large string/binary values at 64 KiB. See Microsoft SQL Server.
What stays on disk
History stores query text and execution metadata, including error messages; it does not store result rows or connection passwords. Saved queries store the text you choose to save. Literal values in that text remain part of the local query library. Deleting a connection removes its history and connection-specific saved queries; queries shared across the same engine remain available.