Round-tripping Campfire and Jellyfin SQLite schemas exposed type and index losses, since fixed

The author, who builds the desktop ERD tool Schemity, tested whether a diagram tool can read a SQLite schema and rebuild an identical database file. They used two open-source schemas, Campfire v1.5.2 (Rails 8) and Jellyfin 12.2 (Entity Framework Core 10). Before recent fixes, Campfire's declared column types were replaced by affinity names, which broke account creation, and Jellyfin's partial and expression indexes were dropped. After the fixes, Jellyfin matches its original with no catalog differences, and Campfire differs only in its FTS5 search table. All 18 behaviour probes across both schemas then matched the originals. This post is the fourth in a series testing round-trip fidelity across several database engines.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in