Meal-Planner

Public Access

Files

T

admin f5fb7558c4 fix(migration): simplify aisle migration + add persistent backup script

- Drop the empty batch_alter_table block and the meaningless
  set_config call from migration 0015. Temp tables still persist
  for the migration's session (Alembic's transactional_ddl).
- New backend/scripts/persist_aisle_backup.sql creates
  public.ingredient_aisle_backup_0015 and
  public.grocery_item_aisle_backup_0015 permanent tables for
  operators who want a recoverable record beyond the migration.
- Update Review/sprint2-verification.md, Review/ui-nielsen-audit.md
  and fix-ui-audit.md with the correct container-based deploy
  steps: docker compose exec db psql -U mealplanner -d mealplanner
  -f /dev/stdin < ...sql. Host psql is not available on the
  deployment host; the db runs inside the container.

2026-06-03 17:41:59 -07:00

0001_initial_migration.py

feat: phase r1+r2 recovery + r3-0 swiftly api ingestion

2026-05-05 14:08:19 -07:00

0002_seed_data.py

feat: phase r1+r2 recovery + r3-0 swiftly api ingestion

2026-05-05 14:08:19 -07:00

0003_grocery_item_description.py

feat: phase r1+r2 recovery + r3-0 swiftly api ingestion

2026-05-05 14:08:19 -07:00

0004_family_profile_calorie_target.py

feat: phase r1+r2 recovery + r3-0 swiftly api ingestion