Copy a fork's index in the database instead of rebuilding it
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
A fork or duplicate takes its source's index as it stands, copied row by row with one INSERT ... SELECT per table, with its first revision's settings from saved history, instead of reading the head as a whole document and rebuilding the index in Node. Search vectors are kept by a trigger instead of generated, so the copy takes them as they are. Comparisons, indexes awaiting a repair and heads saved as documents are rebuilt as before. Forking 200,000 moments drops from about 110-120 s to 23-33 s. Fixes #140. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/c95f57a440a9776220e5107583cfcf9e715b54da
Related
Open Copy a fork's index in the database instead of rebuilding it in the timeline