Connect to PostgreSQL
Choose New Connection from the command palette. Enter host, port, database, username, password, TLS, and read-only options. Saved connection records reference Tide's secret service rather than embedding passwords.
New connections default to read-only. Tide applies client-side checks and requests a read-only PostgreSQL session. Use a database role without write privileges when the server must enforce authorization.
Write a query beside your code
Open New Query and select a connection. Use Ctrl+R, Ctrl+Enter, or F5 while the SQL editor has focus to execute. Ctrl+Space offers SQL completion in that context.
The SQL editor and its results share a tab. You can place it next to your source, a terminal, or another query using the usual pane controls.
Browse the schema
Browse Schema opens schemas, tables, views, and columns. Inspect definitions or open a query for the selected object. Schema-aware completion helps you use the connected database's names.
Work with results
Results appear beneath the SQL editor. Click a column header to sort; click again to reverse direction. Keyboard controls move between rows and columns, open row details, refresh, switch view modes, sort, and export.
Export writes the displayed result data to a destination you choose. Query history can view or insert saved SQL without executing it; execution is a separate explicit action. Filter history by connection and mark favorites for reuse.
Eligible row changes
Update, delete, and add-row workflows require a writable connection and suitable table metadata and identity. Typed fields and primary keys are checked before mutation. An arbitrary query result is not automatically editable.
Review the target connection, table, and action before confirming. Broad, destructive, mixed, or unknown operations require confirmation.
Credentials and TLS
Tide can use a platform keychain, read-only environment values, or an unlocked encrypted-file secret provider. TLS modes preserve the selected verification policy. Configure certificate authority and hostname verification for a verified connection.
History lives in Tide's data root and can be disabled with session.databaseQueryHistory. Redact credentials and sensitive query data before sharing logs or exports.