Update Postgres docs to use prisma-client generator

[AmanVarshney01]

Summary by CodeRabbit

• Documentation

  • Updated PostgreSQL integration guides with new Prisma v7 configuration patterns, including adapter-based connection setup and generated client output structure.

• Dependency Updates

  • Prisma ecosystem packages updated to v7.0.0; introduced new PostgreSQL adapter package for enhanced connection management.

• Configuration Changes

  • Postinstall scripts updated to reflect new Prisma generation workflow; import paths adjusted for generated client locations.

[coderabbitai]

Walkthrough

This PR updates PostgreSQL integration documentation files to reflect Prisma v7 changes: the generator provider changes from "prisma-client-js" to "prisma-client" with an output path "./generated", imports are updated to use the generated client, and the postinstall script removes the "--no-engine" flag. The Netlify example additionally integrates the PrismaPg adapter.

Changes

Cohort / File(s)	Summary
Prisma generator and import path updates content/250-postgres/350-integrations/100-netlify.mdx, content/250-postgres/400-query-optimization/100-setup.mdx	Generator provider changed from "prisma-client-js" to "prisma-client" with output path "./generated" added; PrismaClient import paths updated to reference generated client location
Adapter integration pattern content/250-postgres/350-integrations/100-netlify.mdx	Introduces PrismaPg adapter usage from "@prisma/adapter-pg"; PrismaClient now instantiated with adapter configuration using new PrismaClient({ adapter })
Dependency version bumps content/250-postgres/350-integrations/100-netlify.mdx	"@prisma/client" and "prisma" updated to "^7.0.0"; new dependency "@prisma/adapter-pg" added at "^7.0.0"
Postinstall script normalization content/250-postgres/350-integrations/100-netlify.mdx, content/250-postgres/350-integrations/200-vercel.mdx	"prisma generate --no-engine" replaced with "prisma generate"; related documentation notes removed

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Changes follow a consistent migration pattern repeated across multiple files
• Primary focus is documentation accuracy rather than complex logic
• Key areas requiring attention:
  • Verify PrismaPg adapter instantiation syntax matches the actual API in v7.0.0
  • Confirm generated client import path "./generated" aligns with Prisma's output behavior
  • Ensure dependency versions (v7.0.0) are correct and available
  • Check that all examples maintain consistency in the adapter usage pattern

Possibly related PRs

• fix: add callout to Prisma Config DC-4961 #7095: Documents the introduction of custom output paths and the prisma generate workflow pattern that this PR now applies to code examples
• feat: updated docs for 6.15 #7083: Updates documentation to introduce the prisma-client generator multi-file output layout and driver adapters/PrismaPg usage, directly overlapping with the adapter integration pattern shown here
• docs: Update TypedSql docs to include custom sql folder location #7161: Modifies the same Prisma generator block pattern and updates imports to generated client paths across documentation examples

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately captures the main purpose of the changeset: updating PostgreSQL documentation to use the new prisma-client generator instead of prisma-client-js, including adapter integration and dependency updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 87eba65 and 4145148.

📒 Files selected for processing (3)

• content/250-postgres/350-integrations/100-netlify.mdx (6 hunks)
• content/250-postgres/350-integrations/200-vercel.mdx (1 hunks)
• content/250-postgres/400-query-optimization/100-setup.mdx (2 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.

Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.

📚 Learning: 2025-08-11T09:40:55.237Z

Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.

Applied to files:

• content/250-postgres/350-integrations/200-vercel.mdx
• content/250-postgres/350-integrations/100-netlify.mdx
• content/250-postgres/400-query-optimization/100-setup.mdx

📚 Learning: 2025-10-09T21:32:50.340Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.

Applied to files:

• content/250-postgres/350-integrations/200-vercel.mdx
• content/250-postgres/350-integrations/100-netlify.mdx
• content/250-postgres/400-query-optimization/100-setup.mdx

📚 Learning: 2025-10-08T16:23:00.388Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.

Applied to files:

• content/250-postgres/350-integrations/100-netlify.mdx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Check links
• GitHub Check: Check internal links
• GitHub Check: runner / linkspector
• GitHub Check: Cloudflare Pages

🔇 Additional comments (8)

content/250-postgres/350-integrations/200-vercel.mdx (1)

89-99: Postinstall script update aligns with Prisma v7 changes.

The removal of the --no-engine flag from the postinstall script is the correct approach for Prisma v7, simplifying the setup and reflecting the platform's streamlined defaults for this version.

content/250-postgres/400-query-optimization/100-setup.mdx (2)

48-52: Generator configuration update correctly reflects Prisma v7 structure.

The provider change to "prisma-client" with explicit output path is the new pattern. The previewFeatures configuration for backward compatibility with older Prisma versions (4.2.0–6.1.0) is thoughtfully preserved in this collapsible details section.

---

70-76: Import path correctly points to generated client.

The relative import path ../prisma/generated/client properly resolves to the output location specified in the generator config. The extension imports and chained application of Optimize and Accelerate extensions follow the correct pattern.

content/250-postgres/350-integrations/100-netlify.mdx (5)

54-57: Generator configuration updated consistently.

The provider and output path changes align with the Prisma v7 migration across all documentation examples.

---

131-134: Schema example correctly shows v7 generator pattern.

The generator block properly demonstrates the new provider and explicit output path structure for the Netlify + Next.js example.

---

164-168: PrismaPg adapter pattern is clearly demonstrated.

The code shows the new Prisma v7 adapter-based approach: importing the generated client, instantiating the PrismaPg adapter with the database connection string, and passing it to the PrismaClient constructor. This is a significant architectural shift from direct @prisma/client usage and is well-illustrated for users migrating to v7.

---

206-242: Dependency versions correctly bumped to Prisma v7.

All three critical dependencies—@prisma/client, @prisma/adapter-pg, and the prisma dev dependency—are updated to ^7.0.0, providing a consistent and clear migration path for users following this guide. The addition of the adapter-pg dependency is properly shown in the package.json alongside the Netlify and other runtime dependencies.

---

217-217: Postinstall script aligns with v7 best practices.

Consistent with the Vercel example, the postinstall script now uses prisma generate without the --no-engine flag, reflecting Prisma v7's simplified deployment model.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

[github-actions]

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

• This PR does not change any pages in a way that would require a redirect.

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	4145148
Status:	✅  Deploy successful!
Preview URL:	https://2f3551cf.docs-51g.pages.dev
Branch Preview URL:	https://dc-5034-docs-update-postgres.docs-51g.pages.dev

View logs

[github-actions]

🍈 Lychee Link Check Report

Note: Links are cached for 5 minutes. Failed links (timeouts, rate limits) are retried in a second run with longer timeout.

📊 Results Overview

Status	Count
🔍 Total	2405
✅ Successful	2123
⏳ Timeouts	0
🔀 Redirected	259
👻 Excluded	21
❓ Unknown	0
🚫 Errors	1
⛔ Unsupported	1

Errors per input

Errors in 200-orm/800-more/600-help-and-troubleshooting/050-dataguide/02-introduction-to-data-types.mdx

• [ERROR] https://www.gnu.org/software/coreutils/manual/html_node/date-invocation.html#date-invocation | Error (cached)