Why Tablyne for SQLite

Open SQLite files locally or through remote transports, inspect the query plan and stage row-token-checked edits.

The most-voted request for this workflow is SQLite over SSH - 45 votes when we checked on Nov 12, 2026. Tablyne’s SQLite form keeps the database as a file or remote source, then applies the same deliberate sequence: open, browse, stage, review and commit.

A file, not a fake server

The local connection uses File on this computer. There is no host, port, user or password because the database is the file. The path must already exist; Tablyne does not create an empty .db for a wrong path.

The source selector also includes Turso / libSQL and Server over SSH. These paths are intentionally described here because the implementation has separate remote transports: a libSQL address and token, or the server’s own sqlite3 process for a remote file.

Edits checked against the row

SQLite does not provide a built-in row version column for this workflow. Tablyne computes a token from the row’s raw SQLite values and stores it with the staged edit. Before writing, it re-reads the row and compares the token. A changed row rejects the batch instead of silently overwriting the other session’s work.

The review SQL shows BEGIN IMMEDIATE, the re-read SELECT, the UPDATE or DELETE, and COMMIT. The token comparison itself is in application memory, so the SQL text explains that step instead of pretending it is a SQLite predicate.

Where to go next

  1. Connect to SQLite and choose the source.
  2. Read safe mode and review before editing a shared file.
  3. Open the SQLite Browser page.

Use Ctrl+S to save pending changes, Ctrl+Z to undo and Ctrl+Y to redo.