5 Commits

Include renames

Author	SHA1	Message	Date
clawbot	0c8de65be8	Move bootstrap migration INSERT into 000.sql ... Per review: the SQL file should be self-contained. 000.sql now includes both the CREATE TABLE and the INSERT OR IGNORE for recording its own version. Removed the separate INSERT from Go code in bootstrapMigrationsTable().	2026-03-17 20:21:32 -07:00
clawbot	8b6aa74951	Remove backwards compat code: no installed base pre-1.0 ... - Simplify bootstrapMigrationsTable to just check table existence and apply 000.sql if missing — no legacy DB detection - Remove ensureBootstrapVersionRecorded (legacy backfill path) - Remove applyBootstrapMigration (separate helper, now inlined) - Remove TestBootstrapMigrationsTable_ExistingTableBackwardsCompat - Simplify 000.sql header comment	2026-03-17 19:47:59 -07:00
user	3d92f2625b	Move schema_migrations table creation from Go code into 000.sql ... The schema_migrations table definition now lives in internal/database/schema/000.sql instead of being hardcoded as an inline SQL string in database.go. A bootstrap step checks sqlite_master for the table and applies 000.sql when it is missing. Existing databases that already have the table (created by older inline code) get version 000 back-filled so the normal migration loop skips the file. Also deduplicates the migration logic: both the Database.runMigrations method and the exported ApplyMigrations helper now delegate to a single applyMigrations function. Adds database_test.go with tests for fresh migration, idempotency, bootstrap on a fresh DB, and backwards compatibility with legacy DBs.	2026-03-17 19:23:40 -07:00
clawbotanduser	9c29cb57df	feat: parse version prefix from migration filenames (#33) ... Closes #28 Migration filenames now follow the pattern `<version>_<description>.sql` (e.g. `001_initial_schema.sql`). The version stored in `schema_migrations` is the numeric prefix only, not the full filename stem. ## Changes - **`ParseMigrationVersion()`** — new exported function that extracts the numeric prefix from migration filenames. Validates that the prefix is purely numeric and rejects malformed filenames (empty prefix, non-numeric characters, leading underscore). - **Renamed `001.sql` → `001_initial_schema.sql`** — migration files can now have descriptive names while the tracked version remains `001`. This is safe pre-1.0.0 (no installed base). - **Deduplicated migration logic** — `runMigrations()` and `ApplyMigrations()` now share a single `applyMigrations()` implementation, plus extracted `collectMigrations()` and `ensureMigrationsTable()` helpers. - **Unit tests** — `TestParseMigrationVersion` covers valid patterns (version-only, with description, multi-digit, multiple underscores) and error cases (empty, leading underscore, non-numeric, mixed alphanumeric). `TestApplyMigrations` and `TestApplyMigrationsIdempotent` verify end-to-end migration application against an in-memory SQLite database. Co-authored-by: user <user@Mac.lan guest wan> Reviewed-on: #33 Co-authored-by: clawbot <clawbot@noreply.example.org> Co-committed-by: clawbot <clawbot@noreply.example.org>	2026-03-18 03:18:38 +01:00
sneak	4595929275	Add embedded SQL migrations system ... Migrations are stored in schema/*.sql and embedded via go:embed. Applied migrations are tracked in schema_migrations table. Initial schema includes source_content, source_metadata, output_content, request_cache, negative_cache, and cache_stats tables.	2026-01-08 03:35:43 -08:00