Repository navigation
Link the Postgres import docs and describe Prisma Postgres client-neutrally - #531
Conversation
…trally In "5 ways to host PostgreSQL databases", the third-party offerings line said Prisma Postgres comes "with seamless integration to Prisma's database tools". Say instead that it is managed PostgreSQL behind an ordinary connection string, that any PostgreSQL client or ORM works with it, and that Prisma ORM is optional, as the Prisma Postgres docs state. The FAQ answer on developing locally and deploying to a hosted database now links the Prisma Postgres import docs (pg_dump and pg_restore) and states the PostgreSQL 17 tools requirement from that page. Prettier also re-pads the Backups column of the comparison table, which was misaligned since the "Paid plans" cell was added; no cell text changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
In "5 ways to host PostgreSQL databases", drop the repeated "managed PostgreSQL" from the third-party offerings line, since the section above already says it, and fold the provider list intro into one sentence. The FAQ answer on moving a local database to a hosted one now also says that moving from PostgreSQL 18 needs a separate process that the linked import page does not cover, as that page states. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
✅ Gizmo reviewed 5a92956 — posted 0 inline comment(s) this pass. Open findings: none Change walkthroughChange walkthroughThis PR revises content/04-postgresql/03-5-ways-to-host-postgresql.mdx in two ways: it makes the article's treatment of Prisma Postgres client-neutral, and it adds a data-migration pointer to the local→hosted FAQ. Third-party offerings intro (line 225). The old lead sentence recommended Prisma Postgres "with seamless integration to Prisma's database tools"; the replacement states that Prisma Postgres is reached through an ordinary connection string usable by any PostgreSQL client or ORM ( FAQ: develop locally, deploy to hosted (lines 332-333). A new paragraph points at Migrate a local Postgres database to the cloud (Prisma Postgres) for moving data with Comparison table (lines 277-282). Pure Prettier re-padding of the Backups column, with no cell-text changes.
|
|
This PR changes the following pages (Vercel Preview Deploy links): (Note that links will only be valid after Vercel preview deploy succeeded) |
![prisma-gizmo[bot]](https://avatars.githubusercontent.com/in/4769794?s=60&v=4){kind=small}
|
@prisma-gizmo review |
This branch was successfully deployed
1 participant
"5 ways to host PostgreSQL databases" compares local, self-managed, cloud-provider and third-party PostgreSQL hosting, with an FAQ.
Changes
psql,node-postgres, Kysely, Drizzle or Prisma ORM), and Prisma ORM is optional. This also drops the recommendation wording ("is recommended for developers who want a fully managed PostgreSQL solution"). The provider list intro is folded into the same paragraph.pg_dumpandpg_restore, linking Migrate a local Postgres database to the cloud (Prisma Postgres). It states the PostgreSQL 17 tools requirement, that the source must run 17 or older, and that moving from 18 needs a separate process the page does not cover.prettier --check). No cell text changes.lastUpdatedbump, per the repo's AGENTS.md ("Don't bump dates" unless an article is substantively corrected and re-tested), matching Describe Prisma Postgres in the PostgreSQL hosting guide with documented facts #527, Limit backup wording in Prisma Postgres CTAs to paid plans #528 and Point the local PostgreSQL guides to moving a database online #529.Sources checked 2026-10-19
pg_dumpcannot dump an 18 server, and moving from 18 needs a separate process. The URL returns 200 text/html.Checks
prettier --checkon the changed file: pass.npm test: 78/78 pass.npm run typecheck: pass.ADD_PREFIX=true npm run build: pass, including the internal link and anchor check.🤖 Generated with Claude Code