Keep saved history as rows instead of whole documents
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
Each version of a timeline's moments, durations, relationships and settings is now a row valid from the revision that saved it until the one that changed it (server/history.mjs). A save writes only the versions it changed, and reading revision n selects the rows valid at n, so no save copies the whole timeline and no revision is stored as one jsonb value. - Saves (in place or rebuilt), forks, syncs and merges record revisions kept as rows, charged the bytes of the versions they wrote; whole-timeline comparisons run a page of 20,000 entities at a time. - Migrating starts history for existing timelines at their current revision with one copy made in the database; earlier revisions keep their snapshots and patches. A timeline starting at a save is copied without lookups, and statistics are refreshed after large copies. - Versions are immutable apart from ending once (a trigger); pruning and deletion remove the versions no remaining revision sees. - Pull requests still store whole documents, refused with a reason over 200 MB; the log importer's storage estimate follows the new charges. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/d7a9a23c6c80362f019be0d53c34d6660f21c8d8
Open Keep saved history as rows instead of whole documents in the timeline