Move schema_migrations table creation into 000.sql with INTEGER version column #58

Open
clawbot wants to merge 2 commits from feat/migration-bootstrap-000sql into main

2 Commits

Author SHA1 Message Date
clawbot
197f09066b test: add migration engine tests
All checks were successful
check / check (pull_request) Successful in 4m26s
Add three tests requested in review:
- TestParseMigrationVersion: table-driven test with 9 cases covering valid
  filenames, descriptions, invalid alpha/mixed, and empty string
- TestApplyMigrations_Idempotent: verifies running migrations twice is a
  no-op with no duplicate rows in schema_migrations
- TestBootstrapMigrationsTable_FreshDatabase: isolation test verifying
  bootstrap creates schema_migrations table with version 0 row
2026-03-26 09:55:35 -07:00
clawbot
eb1d5dd561 Move schema_migrations table creation into 000.sql with INTEGER version column
All checks were successful
check / check (pull_request) Successful in 2m30s
Replace the monolithic schema.sql embed with a numbered migration system
following the pixa pattern:

- Add schema/000.sql: bootstrap migration creating schema_migrations table
  with INTEGER PRIMARY KEY version column and applied_at timestamp
- Move full schema to schema/001.sql (renamed from schema.sql)
- Remove redundant schema/008_uploads.sql (uploads table already in main schema)
- Rewrite database.go migration logic:
  - Embed schema/*.sql directory instead of single schema.sql
  - bootstrapMigrationsTable() checks for table existence, applies 000.sql
  - applyMigrations() iterates numbered files, skips already-applied versions
  - ParseMigrationVersion() extracts version from filenames (e.g. 001.sql)
  - Go code does zero INSERTs for bootstrap — 000.sql is self-contained
- Update database_test.go to verify schema_migrations table exists
2026-03-26 09:45:17 -07:00