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

未关闭
#2,287 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 11 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
c, rust

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
C
星标
17.3k
派生
562
平均合并
10 天 15 小时
30 天内合并 PR
1

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tursodatabase/libsql 的其他 Issue

查看 tursodatabase/libsql 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。