An illustrative session
A small investigation with a reusable lesson: inspect the query before replacing the database.
Synthetic, condensed example. This static page illustrates the reading experience; it does not connect to a private instance or offer working voting. The platform uses server-resolved session/node paths; this static sample uses fragment links.
Our session library is growing, and loading a long session gets slower. Do we need to move to a different database?
First, inspect how we load the visible transcript window. A filter, sort, and limit should work together.
EXPLAIN QUERY PLAN SELECT * FROM nodes WHERE session_id = ? AND ordinal >= ? ORDER BY ordinal LIMIT 30;
SEARCH nodes USING INDEX session_id_ordinal (session_id=? AND ordinal>?)
With a compound index matching the query, the reader can load a bounded slice instead of scanning the entire transcript.
Match the index to the filter and sort. Keep the initial page small. Load older entries when readers request them, and resolve a deep link directly.
The reusable lesson isn't “SQLite is always fast.” It's “measure the query and payload before adding another service.”