Query history, saved queries and export
The Console for PostgreSQL, MySQL, 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 result table, or JSON for Redis replies. 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.
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.