Add schema v2 with stable IDs and migration - #14
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here's the same work rewritten to match the lnk #23 voice (imperative title,
## Summaryopener, bold-lead-in bullets, a command table, guardrails section,make checkcloser):Summary
Adds schema v2: stable IDs and
created_at/updated_aton every entity (Shelf, Collection, Mark), plus an explicitbook migratecommand to upgrade existing v1 shelf files in place. Completes the schema-v2 spine ahead of the SQLite index work and the v2.0.0 release.What's new
catalog_id), decoupling identity from the human-readable name so renames stop being destructive.created_at/updated_aton all entities, plusdeleted_aton Mark (schema only; soft-delete behavior lands separately).book migrate- non-interactive v1-to-v2 upgrade, gated behind--confirmlike other writes.Usage
book migrateshelf.d/to v2 schemaBehavior changes / guardrails
book migrateis idempotent: re-running on v2 files is a no-op and reports "N upgraded, M already v2"..bakper file.Testing
.bakfallback coverage.make checkruns fmt, vet, lint, and tests; all green.