keith/MeshVault
1
0 Fork 0
Code Issues 44 Pull Requests Actions Packages Projects Releases Wiki Activity

Database migration tooling #12

New Issue
Open
opened 2026-10-10 22:18:26 +00:00 by keith · 1 comment
keith commented 2026-10-10 22:18:26 +00:00
Owner
Copy link
Copy source

Schema changes must be versioned and repeatable from the start.

Scope

  • Forward migration runner with ordered, versioned files
  • Applied-migration tracking table
  • Runs automatically on container start or via an explicit task target
  • Safe to run repeatedly

Acceptance criteria

  • Migrations apply to an empty database to produce the current schema
  • Re-running applies nothing and exits successfully
  • Failure aborts with a clear message and leaves tracking consistent

Blocked by: #6, #8

Schema changes must be versioned and repeatable from the start. ## Scope - Forward migration runner with ordered, versioned files - Applied-migration tracking table - Runs automatically on container start or via an explicit task target - Safe to run repeatedly ## Acceptance criteria - [ ] Migrations apply to an empty database to produce the current schema - [ ] Re-running applies nothing and exits successfully - [ ] Failure aborts with a clear message and leaves tracking consistent --- Blocked by: #6, #8
keith added this to the M2 - Data Model & Migrations milestone 2026-10-10 22:18:26 +00:00
keith added the area:dbpriority:hightype:chore labels 2026-10-10 22:18:26 +00:00
keith commented 2026-10-12 18:55:27 +00:00
Author
Owner
Copy link
Copy source

Acceptance reconciliation at c1ef2ee: keeping open. PG fixtures execute production migrations, but direct rollback and clean-start migration acceptance must still be verified independently. This is a source/test review, not a newly executed crash or restore experiment. Fresh Windows suite: 291 tests, 1801 assertions, 22 skips; lint passes. PostgreSQL fixture success does not waive these feature criteria.

Acceptance reconciliation at c1ef2ee: keeping open. PG fixtures execute production migrations, but direct rollback and clean-start migration acceptance must still be verified independently. This is a source/test review, not a newly executed crash or restore experiment. Fresh Windows suite: 291 tests, 1801 assertions, 22 skips; lint passes. PostgreSQL fixture success does not waive these feature criteria.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
area:backend
PHP application logic
 area:db
PostgreSQL schema and migrations
 area:frontend
PHP views, Tailwind, browser JS
 area:indexer
Scanning, hashing, import pipeline
 area:infra
Docker, CI, deployment
 priority:high
Blocking or critical path
 priority:low
Nice to have
 priority:medium
Normal priority
 type:bug
Defect
 type:chore
Tooling, scaffolding, maintenance
 type:decision
Architecture decision record
 type:docs
Documentation
 type:feature
New user-facing capability
No labels area:db priority:high type:chore
Milestone
No items
No Milestone M2 - Data Model & Migrations
Projects
Clear projects
No projects
Assignees
Clear assignees
keith (Keith Solomon)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: keith/MeshVault#12