Phials documentation
Developer docs

Database

Phials can open SQLite database files in a read-only preview, so you can look at tables and cell values without changing the file on disk. This helps when you keep local app data, exports, or small analytical databases alongside your other files.

What you can open

The database preview appears for files whose names end with one of these extensions:

db, sqlite, sqlite3, db3, s3db, sl3

Your system may also tag some of these as SQLite MIME types, and Phials treats them the same way.

Prerequisites

  • The database file must be readable from the folder you have open in Phials.
  • The preview only lists normal user tables, the kind you would see in a schema browser. Internal SQLite catalog tables stay hidden, and the preview does not run arbitrary SQL. You browse one table at a time through the on-screen controls.

How to browse a database

  1. Select the file in the file list so the preview shows the database preview, or open it however you usually open previews for that file type.

  2. Wait for the database to open. You will briefly see an “Opening database…” state while Phials reads the schema.

  3. Pick a table from the dropdown at the top of the preview. Each option shows the table name, and when it is available, a row count appears so you can tell large tables apart from small ones.

  4. Read the grid. Values appear in columns matching the table. Empty SQL nulls are labeled NULL. Binary (BLOB) columns are not shown as raw bytes. Instead you see a short placeholder that includes the size in bytes. Other structured values may appear as readable text or JSON.

  5. Move through rows with the Previous page and Next page controls. The preview loads data in pages (by default 100 rows per page). A compact label shows which rows you are viewing and, when the database reports it, the total row count.

  6. Sort within the current page by clicking a column header where sorting is available. Sorting applies to the rows currently loaded, not the entire table at once.

  7. Open fullscreen when you need more space for wide tables or long text:

    • Use the expand / fullscreen control in the preview toolbar, or
    • Double-click the database file in the file list. Unless you have changed Phials’ double-click settings for that extension, this opens the fullscreen database preview instead of sending the file to another app.

    In fullscreen, the layout matches the sidebar preview but without the redundant fullscreen button, since you are already there.

If something goes wrong

  • “Failed to open database” usually means the file is missing, locked by another program, corrupted, or not readable from its path. Close other apps that might hold an exclusive lock, confirm the file still exists, and try again.
  • “No user tables in this database.” means Phials did not find any non-system tables to show. Empty files or databases that only contain special constructs can look like this.
  • Per-table errors can still appear for individual tables in rare cases, for example if metadata for a specific table cannot be read. Pick another table from the dropdown if one misbehaves.

What this preview does not do

  • No editing: The connection is read-only. You cannot change data, run UPDATE/DELETE, or alter the schema from this preview.
  • No arbitrary queries: There is no SQL console here, only paginated table browsing.
  • No raw BLOB export: Large binary fields are summarized rather than opened as files.

Tips

  • For very wide tables, fullscreen and column resizing (where the table UI supports it) make scanning easier.
  • If double-clicking a .db file opens something other than Phials, check Default behaviors so it stays on preview when you want the in-app database viewer.