`/dump` on Turso Cloud writes the first FTS5 shadow table twice, and still emits unescaped virtual-table SQL
Maintainers usually reply within 11 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- backend-api-design, databases
Research direction
Start by comparing the Cloud /dump output with the clean turso dev result, then inspect change 63ba6b8d5 and the /dump implementation. Done means the virtual-table SQL is escaped and the first FTS5 shadow-table block is emitted only once, with a regression test or reproducible check covering restoration with sqlite3.
Written by the indexing model from the issue text.
Description
Summary
A dump of a libSQL database on Turso Cloud that contains an FTS5 table cannot be restored with sqlite3 without errors. Two things are wrong in the output:
- The block for the first shadow table (
<name>_data: itsCREATE TABLE IF NOT EXISTSand all of itsINSERTrows) is written twice, back to back and byte-identical. Restoring fails withUNIQUE constraint failed: <name>_data.id. - The virtual-table definition is written without escaping its single quotes. This was fixed in 63ba6b8d5 ("fix: pass argument through Escaped interface", 2025-10-08), but no
libsql-serverrelease contains it (the latest is v0.24.32 from 2025-02-14) and Turso Cloud still produces the old output as of 2026-10-04.
Details
The table was created like this, so the virtual table precedes its shadow tables in sqlite_schema (rowid order: notes_fts, notes_fts_data, notes_fts_idx, notes_fts_docsize, notes_fts_config):
CREATE VIRTUAL TABLE notes_fts USING fts5(
title,
summary,
content='notes',
content_rowid='rowid',
tokenize='trigram'
);
Dump taken with turso db shell "https://<db>.turso.io?authToken=…" .dump (CLI v1.0.33, which prints the response of GET /dump as is), region aws-ap-northeast-1. Table names changed, structure unchanged:
PRAGMA writable_schema=ON;
INSERT INTO sqlite_schema(type,name,tbl_name,rootpage,sql) VALUES('table','notes_fts','notes_fts',0,'CREATE VIRTUAL TABLE notes_fts USING fts5(
title,
summary,
content='notes',
content_rowid='rowid',
tokenize='trigram'
)');
CREATE TABLE IF NOT EXISTS 'notes_fts_data'(id INTEGER PRIMARY KEY, block BLOB);
INSERT INTO notes_fts_data VALUES(1,X'…');
… 30 rows
CREATE TABLE IF NOT EXISTS 'notes_fts_data'(id INTEGER PRIMARY KEY, block BLOB);
INSERT INTO notes_fts_data VALUES(1,X'…');
… the same 30 rows
CREATE TABLE IF NOT EXISTS 'notes_fts_idx'(segid, term, pgno, PRIMARY KEY(segid, term)) WITHOUT ROWID;
…
- Seen in two dumps taken a day apart (2026-10-03 and 2026-10-04). No other table is repeated. A second Cloud database without virtual tables dumps cleanly.
- Not reproducible locally: the same table created in the same order and served by
turso dev(sqld 0.24.32) is dumped once.
Effect
sqlite3 -bail restored.db < dump.sql stops at the virtual-table statement with a syntax error and, once that statement is fixed by hand, at the repeated rows. Without -bail the restore finishes, but the FTS table is missing while its triggers remain, so every insert into the content table fails with no such table: main.notes_fts.
Ask
- A
libsql-serverrelease, and a Turso Cloud deploy, that include 63ba6b8d5. - A look at why the Cloud
/dumprepeats the first shadow table.
- Dominant language
- C
- Stars
- 17.3k
- Forks
- 562
- Avg merge
- 10d 15h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tursodatabase/libsql
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tursodatabase/libsql#2320 ·
Maintainers usually reply within 11 days
-
`cloudflare` feature: hrana streams are never closedPossibly taken @pcbeingused333 claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tursodatabase/libsql#2312 ·
Maintainers usually reply within 11 days
-
bottomless: finished S3 upload tasks are never reaped, so sqld memory grows by ~10 KB per WAL batchPossibly taken @pavanmanishd claimed this 25 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
tursodatabase/libsql#2298 · 1 comment ·
Maintainers usually reply within 11 days
-
Rust local Row::get_value truncates embedded NUL TEXT and panics on malformed UTF-8 (0.9.30)Possibly taken @Sanjays2402 claimed this 35 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tursodatabase/libsql#2285 ·
Maintainers usually reply within 11 days
-
libsql-ffi: broken builds under Nix on macOSPossibly taken @frectonz claimed this 85 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
tursodatabase/libsql#2275 ·
Maintainers usually reply within 11 days
All issues in tursodatabase/libsql
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libretro/parallel-n64#858 ·