SQLite
Connect to a local SQLite file path and browse or query it through the SQLite driver.
Database
Database Documentation
Unfour supports verified SQLite, PostgreSQL, and MySQL database workflows for saved connections, schema and data browsing, supported row editing, and SQL execution; compatible MariaDB servers use the MySQL driver path where applicable.
Supported databases
PostgreSQL
Connect with host, port, database, username, password credential, and the supported PostgreSQL catalog and schema flow.
MySQL and MariaDB
Connect through the MySQL driver. MySQL workflows are verified; compatible MariaDB servers use the same path where their protocol and SQL behavior match.
Create a connection
SQLite
Choose SQLite, give the connection a name, enter the local database file path, choose read-only if needed, then Test and Save.
PostgreSQL
Choose PostgreSQL and enter host, port, database, username, and password. Test the target, review any SSL requirements, then Save.
MySQL
Choose MySQL and enter host, port, database, username, and password. Test the server, then Save. Use this path for a compatible MariaDB server.
Browse databases, schemas, and tables
- Select a saved connection and connect.
- Expand its database or catalog nodes. PostgreSQL can expose schemas inside the active catalog; MySQL exposes databases through the catalog list; SQLite uses its file database directly.
- Expand a table to review columns and primary-key markers.
- Open Structure to inspect available column details, indexes, foreign keys, and generated DDL information.
Browse and edit data
- Open a table to page through 50, 100, or 250 rows at a time.
- Use server-backed text filtering across available columns and sort by a selected column.
- Insert rows into writable tables. Update and delete require a table with primary-key columns so Unfour can identify the target row.
- Connections marked read-only do not expose row editing. Views and tables without a primary key do not allow update or delete.
- Changes are staged first. Preview the generated SQL, revert if needed, then confirm Apply; concurrency predicates help prevent overwriting a row that changed since it was loaded.
Run SQL
- Run Current executes the selection when one exists; otherwise it executes the statement under the cursor.
- Run All splits the editor on statement delimiters while respecting quoted strings and comments, then runs statements sequentially.
- Each statement has its own result tab. Review returned columns and rows, affected rows, messages, and execution duration.
- Mutation and high-impact SQL requires an explicit confirmation before execution. Read-only connections reject writes.
- Stop hides late results from the current run, but the remote database may continue an in-flight statement until it finishes or reaches its timeout.