`/dump` on Turso Cloud writes the first FTS5 shadow table twice, and still emits unescaped virtual-table SQL

Aperta
#2,287 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 11 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, rust

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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:

  1. The block for the first shadow table (<name>_data: its CREATE TABLE IF NOT EXISTS and all of its INSERT rows) is written twice, back to back and byte-identical. Restoring fails with UNIQUE constraint failed: <name>_data.id.
  2. 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-server release 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-server release, and a Turso Cloud deploy, that include 63ba6b8d5.
  • A look at why the Cloud /dump repeats the first shadow table.
Lingua principale
C
Stelle
17.3k
Fork
562
Merge medio
10g 15h
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tursodatabase/libsql

Tutte le issue di tursodatabase/libsql

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.