nalalangan/grocery-app
1
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity
1c50c67410
grocery-app/packages/db/migrations
History
Nico 78893545b2 feat: add location map manager
2026-06-02 01:59:20 -07:00
..
20260328_010000_add_household_store_available_items.sql feat: add store catalog backend 2026-03-28 22:35:34 -07:00
20260329_010000_add_household_store_items.sql feat: add household store item runtime 2026-03-29 01:01:19 -07:00
20260329_020000_fix_household_item_classification_upsert.sql fix(db): restore classification upsert constraint 2026-03-29 12:49:15 -07:00
20260526_010000_custom_store_locations.sql feat: add custom store location backend 2026-05-26 00:38:13 -07:00
20260526_020000_add_household_member_sort_order.sql feat: allow household switcher reordering 2026-05-26 00:58:51 -07:00
20260602_010000_location_maps.sql feat: add location map manager 2026-06-02 01:59:20 -07:00
add_display_name_column.sql chore: establish governance baseline and migration workflow 2026-02-16 01:09:13 -08:00
add_image_columns.sql refactor 2026-02-22 01:27:03 -08:00
add_modified_on_column.sql chore: establish governance baseline and migration workflow 2026-02-16 01:09:13 -08:00
add_notes_column.sql chore: establish governance baseline and migration workflow 2026-02-16 01:09:13 -08:00
create_item_classification_table.sql chore: establish governance baseline and migration workflow 2026-02-16 01:09:13 -08:00
create_sessions_table.sql feat: add db migration for session storage 2026-02-16 01:40:18 -08:00
multi_household_architecture.sql chore: establish governance baseline and migration workflow 2026-02-16 01:09:13 -08:00
README.md refactor 2026-02-22 01:27:03 -08:00
stale-files.json refactor 2026-02-22 01:27:03 -08:00
zz_group_invites_and_join_policies.sql refactor 2026-02-22 01:27:03 -08:00

README.md

Migration Directory

This directory is the canonical location for SQL migrations.

  • Use npm run db:migrate to apply pending migrations.
  • Use npm run db:migrate:status to view applied/pending migrations.
  • Use npm run db:migrate:verify to fail when pending migrations exist.
  • Use npm run db:migrate:new -- <migration-name> to create a new migration file.

Do not place new canonical migrations under backend/migrations.

Stale baseline

  • stale-files.json lists canonical SQL files intentionally treated as stale.
  • Files listed there are skipped by migration commands by default.
  • Add only genuinely new migration files when schema changes are required.