feat(CC-ERATE-000056A): Postgres-first ingestion foundation#50
Open
steven-dracker wants to merge 2 commits intomainfrom
Open
feat(CC-ERATE-000056A): Postgres-first ingestion foundation#50steven-dracker wants to merge 2 commits intomainfrom
steven-dracker wants to merge 2 commits intomainfrom
Conversation
Introduces DatabaseProvider config key ("Sqlite" | "Postgres") alongside
Npgsql.EntityFrameworkCore.PostgreSQL 8.0.11. Startup branches on provider:
SQLite continues to use Migrate(); Postgres uses EnsureCreated() to bypass
SQLite-specific PRAGMA migrations. Provider name is logged at startup.
Default remains SQLite — no behaviour change unless DatabaseProvider=Postgres.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Guard SQLite-specific PRAGMA journal_mode=WAL in migration
20260315000001 with ActiveProvider.Contains("Sqlite") check
- Add Npgsql.EntityFrameworkCore.PostgreSQL 8.0.11 to Infrastructure
project for migration design-time support
- Remove EnsureCreated() from startup — both providers now use Migrate()
- Update startup log: "Database provider: {Provider} — applying migrations"
SQLite path: unchanged, Migrate() runs as before.
Postgres path: Migrate() runs cleanly without hitting PRAGMA.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PRAGMA journal_mode=WAL;in migration20260315000001_AddFundingCommitmentIndexesAndWalwithActiveProvider.Contains("Sqlite")— Postgres migrations now run cleanly without SQLite-specific SQLNpgsql.EntityFrameworkCore.PostgreSQL8.0.11 toErateWorkbench.Infrastructurefor migration design-time supportEnsureCreated()— both providers now use a singleMigrate()call at startupDatabase provider: {Provider} — applying migrationsMigration safety
The PRAGMA guard is the only SQLite-specific SQL across all migrations (confirmed by
grepscan). All other migrations are provider-agnostic.Validation
Database provider: Sqlite — applying migrations,/healthreturns{"status":"ok"}erateuser password is a Keeper-managed credential, full validation to be performed from dude-mcp-01 in next phaseNotes
feature/postgres-local-connectivity(feat(CC-ERATE-000056): add Postgres as configurable database provider (Phase 1) #49) — this PR is a superset; feat(CC-ERATE-000056): add Postgres as configurable database provider (Phase 1) #49 can be closedlocalhostresolves correctly)🤖 Generated with Claude Code