From a query to an answer.
A short tour of connections, SQL files, results, and saved work.
Open your database
Use the file action for an existing SQLite .db, .sqlite, or .sqlite3 file. For PostgreSQL, MySQL, and MariaDB, add a connection with the database hostname, port, database name, and account credentials.
A .sql file contains SQL text; it is not a SQLite database file. Opening a script places it in the editor for review.
Run SQL
SELECT 1 AS connected;Choose Run query, or use Ctrl+Enter on Windows/Linux and Cmd+Enter on macOS. Select part of a script to run that selection. Query errors appear in the workspace so you can correct the SQL and retry.
Use the row limit to keep result sets manageable. Save useful queries in your library and open another tab when you need a separate scratchpad.
Import a SQL script
- Open the SQL file in the editor.
- Select the intended database connection and review the statements.
- Choose Run SQL script and read the import review before executing.
- Refresh the schema and query the imported table to check the result.
Use a dump that matches the target engine. A phpMyAdmin MySQL/MariaDB export is not automatically converted to SQLite. Some engine-specific dump commands may need adjustment. Review destructive statements and use a database backup before a large import.
Work with results
Filter the returned rows, inspect cells, and export your result set as CSV or JSON. The export contains the returned result set, not every row in the database. Change the row limit and rerun if you need more rows.
To delete a row, run a SELECT on one table with its primary key in the result, then choose the row's trash button or right-click the row. The exact DELETE statement is shown before it runs.
Browser file saving and permissions depend on your browser. If a download is blocked, check its downloads panel. Other in-grid editing and interactive transaction management are not part of this beta; use SQL for other changes.
Manage tables and databases
Hover a table in the sidebar and choose its trash button to drop it. The trash button beside the table count drops every table and view. Both ask you to type the table or database name first, and neither can be undone.
For MySQL and MariaDB in the desktop app, the export button writes every table's structure and rows, plus views, into one .sql file that also imports in phpMyAdmin. The import button runs a .sql dump of up to 1 GiB statement by statement, with progress and a stop button.
Stored routines, triggers and events are not exported. If an import statement fails, the statements before it stay applied, so export a backup before importing into a database you need.