chore(memory): noisy-rewrite BDR-080, LRN-080 promoted to rule line
/prune-memory step D (recall feedback 2026-11-12): BDR-080 title and lesson narrowed to the V1-1 DEV recette; LRN-080 status implemented, promoted to rule line .claude/rules/database.md (the rule itself is a separate /feat in this repo).
This commit is contained in:
1 parent
530af1bbfc
commit
fa41bc2e5b
2 files changed
+3
-2
No files matched your search
@@ -596,6 +596,7 @@ Apply: dependency-removal clauses state objective (no declared dep, no script, n
|
||||
Shown on this host (Docker rootless, daemon ip 127.0.0.1, CLI 2.120, images postgres 17.11.0.004, gotrue v2.197.0, storage v1.79.36, postgrest v16.4, mailpit v1.31.3): own network + `-p 127.0.0.1:<57xxx>` per service, no `-v` (images declare no VOLUME → nothing to drop at teardown, `docker rm -f` of literal names suffices). db needs the CLI's role-password init (`/etc/postgresql.schema.sql` via `--entrypoint sh -c`); GoTrue + storage-api migrate their schemas on start; then the CLI's own runners take `--db-url`: `migration up` (records history like DEV), `test db` (pg_prove, rows unchanged), `gen types`. Upgrade path = `--workdir` copy holding the older migrations, then `migration up` from the repo. Real sessions prove what PGlite cannot: concurrency (two psql sessions), GoTrue sign-up/confirm via Mailpit API, PostgREST role refusals, residual GoTrue-admin path. `pg_dump -Fc` as postgres with the container's `$POSTGRES_PASSWORD` dumps auth data too; restore with `--no-owner` keeps every row, prints only managed-object privilege errors.
|
||||
Limits: one host; not a hosted project; vault/realtime/edge absent; CLI may change bind/runner behaviour across versions.
|
||||
Apply: `scripts/db-sandbox.sh` (`pnpm db:sandbox`) for every migration step; DEV changes stay owner actions.
|
||||
- **Status (2026-11-13)**: implemented, promoted to rule line .claude/rules/database.md
|
||||
|
||||
## LRN-081 — `supabase gen types --db-url` to the sandbox needs `?sslmode=disable` (2026-10-25)
|
||||
|
||||
|
||||
Reference in new issue
Block a user