SQLite, DuckDB & Cloudflare D1

SQLite and DuckDB are embedded engines — the file on your disk is the database, and rdSQL opens it directly with no server and no network. Cloudflare D1 is serverless SQLite reached over the Cloudflare REST API.

SQLite / DuckDB#

1. Click New Connection.
2. Set a Connection Name and choose SQLite or DuckDB as the Database Engine.
3. In Database File Path, browse to an existing file (.db, .sqlite, .sqlite3, .duckdb) — or type a new path and rdSQL creates the database there.
4. Click Save. There is nothing to test over the network; the file is opened directly.

DuckDB's rich types — LIST, STRUCT, MAP, ENUM, UNION — are introspected natively rather than flattened to text, so columns read the way DuckDB shows them.

Cloudflare D1#

You need three things from the Cloudflare dashboard:

1. Account ID — visible in the dashboard URL, dash.cloudflare.com/<ACCOUNT_ID>.
2. Database ID (or name) — on the D1 database's page.
3. API token — create one under My Profile → API Tokens with D1 Edit permissions.

Then in rdSQL:

1. Click New Connection and choose Cloudflare D1 as the Database Engine.
2. Fill in the Account ID, API token, and Database ID / Name.
3. Click Test, then Save.

Cloudflare's internal system tables (_cf_%) are filtered out of the explorer automatically to avoid SQLCODE_AUTH (7500) errors, and empty tables get their columns resolved through a PRAGMA table_info fallback.

Troubleshooting#

• File not found — paths resolve on your machine; if the file lives on a network share, make sure it is mounted before opening it.
• D1 auth error — confirm the API token has D1 permissions and hasn't expired.
• SQLite database is locked — SQLite allows one writer at a time; wait for other writers or close external editors before committing cell edits.