LibSQL

libSQL is SQLite-compatible and can run locally or as a remote Turso database. Point TableR at a libSQL URL and, for remote databases, add an auth token.

Overview

TableR connects to libSQL over its URL. A remote Turso database is reached at your-db.turso.io and authenticated with a token; a local libSQL server uses a local URL. Because libSQL is SQLite-compatible, the SQL you already know applies.

• Remote Turso — connect to your-db.turso.io with an auth token.
• Local libSQL — connect to a local libSQL URL.
• SQLite-compatible — the same SQL dialect and functions as SQLite.

Before you start

• A libSQL URL — your-db.turso.io for Turso, or a local libSQL URL.
• An auth token, for a remote / Turso database.
• The port, if your local server does not use 8080.

Connection fields

These defaults match TableR's libSQL connection form. The auth token is stored in the operating system keyring, never in plain configuration files.

Connect with the form

1. 1
   Choose LibSQL

   Open the launcher and pick the LibSQL card.

2. 2
   Enter the libSQL URL

   Use your-db.turso.io for Turso, or your local libSQL URL.

3. 3
   Add the auth token

   Required for remote / Turso databases; saved to the OS keyring.

4. 4
   Set the port (local)

   Local servers use 8080 by default.

5. 5
   Save and connect

   Save the profile so it reappears in the launcher, then connect.

Use a connection string

You can also connect with a libSQL URL. Remote Turso databases use the libsql:// scheme with an auth token.

libsql://your-db.turso.io?authToken=YOUR_TOKEN

• Use libsql:// for remote Turso databases.
• Prefer storing the token in the keyring over embedding it in the URL.
• For a local server, use its libSQL or http(s) URL.

Verify the connection

Once connected, open a SQL tab and run a quick check:

SELECT sqlite_version();
SELECT name FROM sqlite_master WHERE type = 'table';

The first statement returns the SQLite-compatible version; the second lists tables.

Troubleshooting

Next steps