docs: sync from backend 6df113d — marketplace pg backfill

This commit is contained in:
Siavash Sameni
2026-06-01 14:53:35 +04:00
parent 5352a78e96
commit 78707c11a7
4 changed files with 29 additions and 14 deletions

View File

@@ -4,7 +4,7 @@ tags: [data-model, migration, mongodb, postgres, mongoose, helper]
aliases: [Mongo to Postgres, DB Migration Guide, Postgres Migration]
created: 2026-05-31
source: backend/src (automated multi-agent scan)
updated: 2026-05-31 for backend integrate-main-into-development@cab0719
updated: 2026-06-01 for backend integrate-main-into-development@6df113d
---
# MongoDB → PostgreSQL Migration Guide
@@ -17,7 +17,7 @@ updated: 2026-05-31 for backend integrate-main-into-development@cab0719
> **Execution plan:** see the companion [[MongoDB to PostgreSQL Migration Plan (Drizzle)]] for the phased, Drizzle-concrete plan (repository seam, `id_map`, dual-write, per-phase cutover runbook).
> [!warning] Current implementation delta
> This guide started as a migration helper. Backend `integrate-main-into-development@cab0719` now contains the first Postgres implementation layer: Drizzle schemas/migrations through `0008`, `src/db/client.ts`, `id_map`, `pg_dualwrite_gaps`, repository implementations/factory, backfill/verify scripts, conditional `payment_quotes` persistence, and aligned purchase/template request budget validation. The broad service layer is still Mongoose-first and is **not** fully wired through those repositories. Use [[Postgres Runtime Cutover Status]] as the authoritative current-state snapshot.
> This guide started as a migration helper. Backend `integrate-main-into-development@6df113d` now contains the first Postgres implementation layer: Drizzle schemas/migrations through `0008`, `src/db/client.ts`, `id_map`, `pg_dualwrite_gaps`, repository implementations/factory, backfill/verify scripts, conditional `payment_quotes` persistence, and aligned purchase/template request budget validation. Backend `2.8.13` also hardens the PurchaseRequest/SellerOffer backfill runner for marketplace-core dry-runs and selected-offer remapping. The broad service layer is still Mongoose-first and is **not** fully wired through those repositories. Use [[Postgres Runtime Cutover Status]] as the authoritative current-state snapshot.
> [!info] Scan coverage (2026-05-31)
> - **23** Mongoose models (collections)