Will Andersonandcapy-ai-staging[bot] b97ffbfba9 Add indexes on high-traffic foreign keys and sort columns ...

Queries throughout the codebase filter on generations.profile_id,
generations.status, generations.created_at, story_items.story_id,
story_items.generation_id, generation_versions.generation_id, and
profile_samples.profile_id with every request. Without indexes SQLite
falls back to a full table scan; as history grows (hundreds or thousands
of generations) these scans become the dominant latency.

Changes:
- Add index=True on the most-queried FK and sort columns in models.py so
  new installs get them from Base.metadata.create_all
- Add _migrate_add_indexes() called from run_migrations() so existing
  installs get the same indexes on next startup (uses CREATE INDEX IF
  NOT EXISTS — idempotent, <10 ms on any realistic dataset)

2026-10-04 00:00:41 +00:00

..

__init__.py

Add "Log in with browser" cloud device login (#812)

2026-07-05 03:18:30 -07:00

migrations.py

Add indexes on high-traffic foreign keys and sort columns

2026-10-04 00:00:41 +00:00

models.py

Add indexes on high-traffic foreign keys and sort columns

2026-10-04 00:00:41 +00:00

seed.py

fix: store media paths relative to data dir

2026-03-20 15:06:07 -07:00

session.py

perf(db): set the SQLite pragmas from a connect hook and clear WAL sidecars on db reset

2026-10-04 00:00:35 +00:00