(feat) Removes Accelerate specific instructions for Prisma Postgres

[nurul3101]

Completes: #DC-6263

Summary by CodeRabbit

• Documentation

  • Unified database guidance across integration guides: recommend driver-adapter approach, remove legacy extension examples, and standardize install commands.
  • Added informational notes about using alternative drivers (MySQL, SQL Server, SQLite) and updated seeding/migrations guidance.

• New Features

  • Added a Navbar to the Clerk + Next.js example.
  • Chat route/docs updated to persist sessions/messages (save-chat behavior) and added a seed script example for workflows.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This PR replaces many Accelerate/withAccelerate-based Prisma examples with an adapter-based setup (PrismaPg/@prisma/adapter-*) across the guides, updates dependency/install commands to include adapter and pg packages, consolidates tabbed DB instructions into a single advisory, and adds a few adapter-driven code changes and a new saveChat utility.

Changes

Cohort / File(s)	Change Summary
Generic install & guidance updates content/800-guides/010-data-migration.mdx, content/800-guides/130-docker.mdx, content/800-guides/160-tanstack-start.mdx, content/800-guides/180-solid-start.mdx, content/800-guides/190-sveltekit.mdx, content/800-guides/200-clerk-nextjs.mdx, content/800-guides/220-astro.mdx, content/800-guides/230-betterauth-nextjs.mdx, content/800-guides/320-permit-io-access-control.mdx, content/800-guides/360-embed-studio-nextjs.mdx, content/800-guides/370-bun.mdx, content/800-guides/400-betterauth-astro.mdx, content/800-guides/400-deno-integration.mdx, content/800-guides/999-making-guides.mdx	Replace Accelerate-specific install lines with combined installs that include @prisma/adapter-pg, pg, and @types/pg; collapse tabbed DB instructions into a single info admonition recommending appropriate driver adapters for non-Postgres databases; minor init/seed command additions.
Client initialization (adapter migration) content/800-guides/060-migrate-from-drizzle.mdx, content/800-guides/150-multiple-databases.mdx, content/800-guides/190-data-dog.mdx, content/800-guides/330-github-actions.mdx, content/800-guides/340-ai-sdk-nextjs.mdx, content/800-guides/390-hono.mdx, content/800-guides/400-deno-integration.mdx	Remove withAccelerate/accelerate wiring; add PrismaPg adapter instantiation (using DATABASE_URL) and pass adapter into new PrismaClient({ adapter }); update logging/seed/CLI examples where applicable.
Framework/workspace-specific API & export changes content/800-guides/080-turborepo.mdx, content/800-guides/090-nextjs.mdx, content/800-guides/140-use-prisma-in-pnpm-workspaces.mdx, content/800-guides/170-react-router-7.mdx	Replace accelerate-based client with adapter-based client; add exports entry in packages/database/package.json and/or new index.ts re-exports; adjust global singleton/memoization and remove $extends(withAccelerate()).
Migration notices & small edits content/800-guides/050-migrate-from-mongoose.mdx, content/800-guides/060-migrate-from-drizzle.mdx, content/800-guides/160-tanstack-start.mdx, content/800-guides/230-betterauth-nextjs.mdx	Add version/warning notes (e.g., Prisma v6 assumption), reorganize install/generate steps, and remove accelerator-focused examples in favor of adapter guidance.
Feature addition: AI SDK persistence content/800-guides/340-ai-sdk-nextjs.mdx	Add lib/save-chat.ts with exported saveChat(messages, id) to upsert sessions and persist last messages; integrate saveChat into route handler via onFinish callback.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20–30 minutes

• Most edits are a repeated pattern: swap accelerate extension for adapter usage and update install lines (low cognitive load).
• Several files contain unique API/export changes or new logic (exports in packages, prisma.config seed addition, saveChat implementation) that require focused review.

Areas to review closely:

• Files adding or changing public exports/exports field (080-turborepo.mdx, workspace package.json examples).
• New persistence logic in 340-ai-sdk-nextjs.mdx (lib/save-chat.ts) for correctness and edge cases.
• Any remaining references to withAccelerate() or @prisma/extension-accelerate that should be fully removed.
• prisma.config.ts changes that introduce migrations.seed — ensure syntax and examples are consistent.

Possibly related PRs

• Docs for Prisma ORM v6.16.0 #7096 — Same code-level migration from Accelerate/extension-based setup to adapter-based (PrismaPg) initialization across guides.
• feat: add migrations.seed to the config docs DC-4716 #7062 — Introduces or aligns with the added migrations.seed configuration used in several updated guides.
• DC-5560 Deno Deploy Integration Guide #7157 — Overlaps on Deno integration changes switching Prisma client examples to adapter-based initialization.

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 describes the primary change across all modified files: systematic removal of Prisma Accelerate-specific setup instructions and replacement with adapter-based approaches throughout the documentation guides.
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 f614bd2 and 83fc24b.

📒 Files selected for processing (1)

• content/800-guides/400-deno-integration.mdx (2 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

[nurul3101]

Also adds instructions to install relevant dependencies required for Prisma 7.

[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:	83fc24b
Status:	⚡️  Build in progress...

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	2234
✅ Successful	2205
⏳ Timeouts	0
🔀 Redirected	5
👻 Excluded	22
❓ 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

• [503] https://www.postgresql.org/message-id/flat/7696-1364569697-520061%40sneakemail.com#df183031e88ecf9e3d77e58ec710c7b1 | Rejected status code (this depends on your "accept" configuration): Service Unavailable

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

content/800-guides/320-permit-io-access-control.mdx (1)

3-3: Minor: metaTitle contains likely typo.

Line 3 has metaTitle: 'How to use Prisma ORM and Prisma Postgres with CPermit.io' but should probably read Permit.io instead of CPermit.io (note the extra "C").

Consider removing the "C" prefix from "CPermit.io".

🧹 Nitpick comments (3)

content/800-guides/220-astro.mdx (1)

287-291: Consider updating the connection pooler recommendation for clarity.

The warning still recommends Accelerate as the primary pooler example. Given that this guide is now focused on the driver adapter pattern (which works without Accelerate), it may be worth broadening the language or adding context that connection poolers like Accelerate are optional additions, not required for the adapter setup shown here. Alternatively, you could mention other pooling options (e.g., PgBouncer) to reflect that Accelerate isn't the only path.

The current advice is technically sound—connection pooling is recommended for production—but slightly misaligned with the PR goal of de-emphasizing Accelerate-specific approaches.

Suggested revision:

 :::warning
-We recommend using a connection pooler (like [Prisma Accelerate](https://www.prisma.io/accelerate)) to manage database connections efficiently.
+For production environments, we recommend using a connection pooler (such as PgBouncer, [Prisma Accelerate](https://www.prisma.io/accelerate), or similar) to manage database connections efficiently.

 If you choose not to use one, **avoid** instantiating `PrismaClient` globally in long-lived environments. Instead, create and dispose of the client per request to prevent exhausting your database connections.
 :::

Alternatively, if you prefer a more generic approach:

 :::warning
-We recommend using a connection pooler (like [Prisma Accelerate](https://www.prisma.io/accelerate)) to manage database connections efficiently.
+For production environments, we recommend using a connection pooler to manage database connections efficiently.

 If you choose not to use one, **avoid** instantiating `PrismaClient` globally in long-lived environments. Instead, create and dispose of the client per request to prevent exhausting your database connections.
 :::

content/800-guides/010-data-migration.mdx (1)

151-159: Informational note about dotenv is now somewhat redundant.

Since line 89 already includes dotenv in the installation command (npm install @prisma/client @prisma/adapter-pg pg dotenv), the note at lines 151-159 about needing to "install the dotenv package" is no longer necessary. Consider removing it to reduce duplication.

content/800-guides/060-migrate-from-drizzle.mdx (1)

264-268: Minor wording refinement for conciseness.

Line 264 uses "in order to have" which is grammatically correct but slightly verbose. Simplify to "so that" or restructure slightly for better flow. As per the learnings, this is a low-priority improvement.

Example:

• Current: "you need to run generate in order to have your schema reflected in TypeScript types"
• Suggested: "you need to run generate so your schema is reflected in TypeScript types"

📜 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 f489364 and f614bd2.

📒 Files selected for processing (26)

• content/800-guides/010-data-migration.mdx (1 hunks)
• content/800-guides/050-migrate-from-mongoose.mdx (1 hunks)
• content/800-guides/060-migrate-from-drizzle.mdx (2 hunks)
• content/800-guides/080-turborepo.mdx (1 hunks)
• content/800-guides/090-nextjs.mdx (2 hunks)
• content/800-guides/130-docker.mdx (1 hunks)
• content/800-guides/140-use-prisma-in-pnpm-workspaces.mdx (2 hunks)
• content/800-guides/150-multiple-databases.mdx (3 hunks)
• content/800-guides/160-tanstack-start.mdx (1 hunks)
• content/800-guides/170-react-router-7.mdx (1 hunks)
• content/800-guides/180-solid-start.mdx (1 hunks)
• content/800-guides/190-data-dog.mdx (3 hunks)
• content/800-guides/190-sveltekit.mdx (1 hunks)
• content/800-guides/200-clerk-nextjs.mdx (1 hunks)
• content/800-guides/220-astro.mdx (1 hunks)
• content/800-guides/230-betterauth-nextjs.mdx (1 hunks)
• content/800-guides/320-permit-io-access-control.mdx (1 hunks)
• content/800-guides/330-github-actions.mdx (2 hunks)
• content/800-guides/340-ai-sdk-nextjs.mdx (1 hunks)
• content/800-guides/350-authjs-nextjs.mdx (1 hunks)
• content/800-guides/360-embed-studio-nextjs.mdx (1 hunks)
• content/800-guides/370-bun.mdx (1 hunks)
• content/800-guides/390-hono.mdx (1 hunks)
• content/800-guides/400-betterauth-astro.mdx (2 hunks)
• content/800-guides/400-deno-integration.mdx (2 hunks)
• content/800-guides/999-making-guides.mdx (2 hunks)

🧰 Additional context used

🧠 Learnings (7)

📓 Common learnings

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-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: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".

Applied to files:

• content/800-guides/060-migrate-from-drizzle.mdx
• content/800-guides/160-tanstack-start.mdx
• content/800-guides/130-docker.mdx
• content/800-guides/350-authjs-nextjs.mdx
• content/800-guides/150-multiple-databases.mdx
• content/800-guides/180-solid-start.mdx
• content/800-guides/390-hono.mdx
• content/800-guides/010-data-migration.mdx
• content/800-guides/230-betterauth-nextjs.mdx
• content/800-guides/090-nextjs.mdx
• content/800-guides/999-making-guides.mdx
• content/800-guides/220-astro.mdx

📚 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/800-guides/060-migrate-from-drizzle.mdx
• content/800-guides/160-tanstack-start.mdx
• content/800-guides/320-permit-io-access-control.mdx
• content/800-guides/390-hono.mdx
• content/800-guides/230-betterauth-nextjs.mdx
• content/800-guides/090-nextjs.mdx
• content/800-guides/170-react-router-7.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/800-guides/060-migrate-from-drizzle.mdx
• content/800-guides/160-tanstack-start.mdx
• content/800-guides/320-permit-io-access-control.mdx
• content/800-guides/130-docker.mdx
• content/800-guides/330-github-actions.mdx
• content/800-guides/340-ai-sdk-nextjs.mdx
• content/800-guides/350-authjs-nextjs.mdx
• content/800-guides/150-multiple-databases.mdx
• content/800-guides/180-solid-start.mdx
• content/800-guides/390-hono.mdx
• content/800-guides/370-bun.mdx
• content/800-guides/140-use-prisma-in-pnpm-workspaces.mdx
• content/800-guides/010-data-migration.mdx
• content/800-guides/360-embed-studio-nextjs.mdx
• content/800-guides/230-betterauth-nextjs.mdx
• content/800-guides/190-sveltekit.mdx
• content/800-guides/090-nextjs.mdx
• content/800-guides/170-react-router-7.mdx
• content/800-guides/080-turborepo.mdx
• content/800-guides/400-betterauth-astro.mdx
• content/800-guides/190-data-dog.mdx
• content/800-guides/999-making-guides.mdx
• content/800-guides/400-deno-integration.mdx
• content/800-guides/200-clerk-nextjs.mdx
• content/800-guides/220-astro.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/800-guides/160-tanstack-start.mdx
• content/800-guides/130-docker.mdx
• content/800-guides/350-authjs-nextjs.mdx
• content/800-guides/150-multiple-databases.mdx
• content/800-guides/010-data-migration.mdx
• content/800-guides/230-betterauth-nextjs.mdx
• content/800-guides/090-nextjs.mdx
• content/800-guides/220-astro.mdx

📚 Learning: 2025-10-08T16:22:57.129Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.

Applied to files:

• content/800-guides/050-migrate-from-mongoose.mdx
• content/800-guides/350-authjs-nextjs.mdx
• content/800-guides/150-multiple-databases.mdx
• content/800-guides/360-embed-studio-nextjs.mdx
• content/800-guides/230-betterauth-nextjs.mdx
• content/800-guides/190-sveltekit.mdx
• content/800-guides/090-nextjs.mdx
• content/800-guides/170-react-router-7.mdx
• content/800-guides/400-betterauth-astro.mdx
• content/800-guides/220-astro.mdx

📚 Learning: 2025-10-14T11:41:08.844Z

Learnt from: carlagn
Repo: prisma/docs PR: 7183
File: content/200-orm/800-more/600-help-and-troubleshooting/050-dataguide/050-database-glossary.mdx:561-567
Timestamp: 2025-10-14T11:41:08.844Z
Learning: Ignore the file `content/200-orm/800-more/600-help-and-troubleshooting/050-dataguide/050-database-glossary.mdx` in future reviews as per user request. Issues in this file were addressed in PR #7185.

Applied to files:

• content/800-guides/350-authjs-nextjs.mdx

🪛 LanguageTool

content/800-guides/060-migrate-from-drizzle.mdx

[style] ~264-~264: Consider a more concise word here.
Context: ...t in Step 1, you need to run generate in order to have your schema reflected in TypeScrip...

(IN_ORDER_TO_PREMIUM)

⏰ 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). (1)

• GitHub Check: Cloudflare Pages

🔇 Additional comments (44)

content/800-guides/220-astro.mdx (1)

53-61: Adapter pattern implementation is consistent and well-documented.

The dependency updates correctly reflect the driver adapter approach, and the new info box (lines 57-61) clearly explains how to swap driver adapters for other databases. All code samples in this guide (seed.ts, prisma.ts) properly use the PrismaPg adapter, maintaining coherence across the entire setup flow.

content/800-guides/200-clerk-nextjs.mdx (3)

223-231: Driver adapter guidance is clearly communicated.

The new info block appropriately advises developers to use corresponding driver adapters for non-PostgreSQL providers. This mirrors the pattern across other guides in the PR and provides helpful context.

---

329-348: PrismaClient initialization correctly uses the PrismaPg adapter.

The adapter pattern is implemented properly with connection string configuration and global singleton management for non-production environments.

---

148-213: Navbar component addition improves the Clerk integration example.

The new component demonstrates best practices for integrating Clerk's authentication UI components and is well-structured for the guide's educational purpose.

content/800-guides/320-permit-io-access-control.mdx (1)

50-58: Installation and driver adapter guidance is consistent with other guides.

The changes properly replace the Accelerate-specific setup with driver adapter instructions and maintain alignment across the documentation suite.

content/800-guides/360-embed-studio-nextjs.mdx (1)

82-90: Dependency changes are correctly applied for Prisma Studio embedding.

The replacement of Accelerate with the PrismaPg adapter and accompanying driver packages is consistent with the PR's migration pattern. The info admonition appropriately guides developers toward database-appropriate adapters.

content/800-guides/230-betterauth-nextjs.mdx (2)

61-69: Installation commands and driver adapter guidance align with the broader migration.

The consolidation from multi-database tabs to a single adapter-based guidance path is a sensible simplification that maintains clarity while reducing redundancy.

---

135-155: PrismaClient initialization properly demonstrates the adapter pattern.

The setup correctly instantiates PrismaPg with connection string and maintains a singleton pattern for development environments.

content/800-guides/170-react-router-7.mdx (1)

50-58: Dependency updates and adapter guidance are consistent and clear.

The changes maintain uniformity with the broader guide updates while providing appropriate context for non-PostgreSQL database choices.

content/800-guides/010-data-migration.mdx (1)

85-96: Installation guidance is updated and driver adapter information is clearly provided.

The changes remove ambiguity about dependency installation and align with the driver adapter approach.

content/800-guides/350-authjs-nextjs.mdx (2)

57-65: Installation and adapter guidance maintain consistency across guides.

The updated dependencies and driver adapter information align with the PR's overall migration strategy and are clearly presented.

---

204-223: PrismaClient adapter initialization is correct and follows established patterns.

The implementation properly uses the PrismaPg adapter with appropriate error handling and development-mode singleton management.

content/800-guides/130-docker.mdx (2)

81-89: Docker guide correctly implements adapter-based Prisma setup.

The installation commands and driver adapter guidance are properly integrated into the Docker containerization examples, maintaining consistency with other updated guides.

---

172-203: Express.js server correctly initializes PrismaClient with the PrismaPg adapter.

The implementation demonstrates proper adapter initialization and connection management within a containerized environment.

content/800-guides/060-migrate-from-drizzle.mdx (1)

53-61: Consistent driver adapter installation pattern.

The installation structure aligns well with the PR's migration strategy: @types/pg and prisma/tsx as dev dependencies, followed by @prisma/adapter-pg, pg, and @prisma/client as runtime dependencies. The accompanying info block gracefully directs non-Postgres users to install the corresponding adapter, reducing the need for database-specific tabs.

content/800-guides/190-sveltekit.mdx (1)

64-72: Installation and driver adapter guidance remains consistent.

The dependency installation and informational note mirror the migrate-from-drizzle guide, maintaining uniformity across documentation. The adapter-based approach is now the standard pattern throughout these guides.

content/800-guides/180-solid-start.mdx (1)

70-78: Consistent adapter pattern established across guides.

Installation and info block align with prior guides in this migration. No inconsistencies detected.

content/800-guides/390-hono.mdx (1)

42-50: Installation pattern consistent throughout this guide set.

The adapter-based installation and driver guidance remain uniform with previous guides.

content/800-guides/400-deno-integration.mdx (1)

107-111: Correct Deno-specific adapter initialization.

The deno install command properly uses the npm: prefix for npm packages, and the PrismaPg adapter is correctly initialized with the connection string. The adapter pattern adapts well to Deno's environment.

Also applies to: 167-176

content/800-guides/160-tanstack-start.mdx (1)

310-318: Installation pattern consistent with established guide standard.

Adapter installation and driver guidance remain aligned across this guide set.

content/800-guides/400-betterauth-astro.mdx (1)

54-62: Correct Astro-specific adapter initialization.

Installation is consistent with other guides. The adapter initialization correctly uses import.meta.env.DATABASE_URL rather than process.env, which is the appropriate pattern for Astro's environment handling.

Also applies to: 125-132

content/800-guides/340-ai-sdk-nextjs.mdx (2)

56-64: Consistent adapter pattern with proper Node.js singleton pattern.

Installation aligns with other guides. The global Prisma instance using the NODE_ENV check is the appropriate pattern for Next.js long-lived environments. The route handler extension to support session ID and message persistence is well-structured.

Also applies to: 165-182, 257-282

---

297-359: Save chat implementation correctly handles session and message persistence.

The saveChat function properly upserts the session and stores the last two messages (avoiding duplicates). The role mapping to enum values and JSON stringification for flexible content storage are both sound approaches.

content/800-guides/330-github-actions.mdx (2)

47-55: Consistent adapter-based setup with clear driver flexibility guidance.

The dependency installation and info admonition about alternative database drivers are well-structured. Users can easily substitute @prisma/adapter-pg for other adapters based on their database choice.

---

142-153: Well-configured seed script using PrismaPg adapter.

The seed script correctly initializes the PrismaPg adapter and passes it to PrismaClient. The pattern of extracting connectionString from environment variables is appropriate for GitHub Actions workflows.

content/800-guides/150-multiple-databases.mdx (2)

64-72: Excellent multi-database setup with adapter flexibility.

Dependencies and driver adapter guidance are consistent. The separation into user and post database clients demonstrates a scalable pattern for multiple database instances.

---

288-310: Properly isolated PrismaClient instances for separate databases.

Each database client correctly initializes its own PrismaPg adapter with its respective connection string environment variable. The global memoization pattern prevents redundant client instantiation in development mode.

content/800-guides/080-turborepo.mdx (2)

96-125: Consistent multi-package-manager dependency installation.

The tabbed installation instructions correctly show the same dependency set across npm, yarn, and pnpm. The info admonition about alternative database drivers is appropriately placed.

---

366-389: Well-structured Prisma package with proper public exports.

The client initialization with PrismaPg adapter is correct, and the index.ts file properly re-exports both the prisma instance and generated types. The Just-in-Time packaging approach with the exports field is documented appropriately.

content/800-guides/190-data-dog.mdx (2)

142-153: Clear driver adapter dependency guidance for Datadog integration.

The dependencies and info admonition are consistent with the broader PR pattern. Users clearly understand they can substitute the PostgreSQL adapter for their database provider.

---

290-342: Adapter-based initialization preserving extension capability.

The PrismaPg adapter is correctly initialized and passed to PrismaClient. The combination with $on("query") logging and $extends for span tagging demonstrates that adapter-based initialization doesn't preclude using Prisma extensions for observability.

content/800-guides/999-making-guides.mdx (3)

94-108: Excellent template code example for adapter-based initialization.

The example correctly demonstrates the PrismaPg adapter pattern and will serve as a clear reference for guide authors. Comments explaining each step are helpful.

---

269-277: Template dependencies and driver flexibility guidance are consistent.

The template installs the correct dependencies and includes the standard info admonition about alternative database drivers. New guide writers have a clear reference.

---

397-406: Template seed script correctly uses PrismaPg adapter.

The seed template matches the patterns established in actual guides. Guide authors can confidently follow this template.

content/800-guides/090-nextjs.mdx (3)

70-78: Consistent Next.js adapter-based setup with driver flexibility.

Dependencies and driver adapter guidance follow the PR-wide pattern. The info admonition allows users to easily adapt for their database choice.

---

286-307: Properly configured Prisma client for Next.js with global memoization.

The PrismaPg adapter is correctly initialized. The global singleton pattern with NODE_ENV check prevents multiple client instances in development, which is best practice for Next.js.

---

680-684: Package.json correctly reflects new adapter dependencies.

The dependencies include @prisma/adapter-pg and pg as required for the adapter-based pattern, alongside @prisma/client.

content/800-guides/140-use-prisma-in-pnpm-workspaces.mdx (2)

96-104: Consistent pnpm workspaces dependency installation and driver guidance.

The dependencies are correctly specified for the pnpm context, and the info admonition about alternative database drivers is properly placed and formatted.

---

213-248: Well-structured shared database package with adapter-based initialization.

The client.ts correctly initializes PrismaPg adapter and uses globalThis for broader environment compatibility. The index.ts properly re-exports both the prisma instance and generated types, making the package consumable across the monorepo.

content/800-guides/370-bun.mdx (4)

45-46: Dependency updates correctly support adapter-based approach.

The addition of @types/pg and pg is necessary and correctly scoped—the driver package pg must be available at runtime for the PrismaPg adapter (instantiated in your db.ts and seed.ts files), and TypeScript types belong in devDependencies. This completes the migration away from Accelerate to a driver adapter pattern.

---

49-53: Info block clarifies adapter selection for different database providers.

This is a helpful addition that explicitly directs users to select the correct adapter when using databases other than PostgreSQL. It acknowledges that while the guide focuses on Prisma Postgres, users may have different needs, and it empowers them with a reference link for complete information.

---

63-67: Setup prompt guidance manages user expectations.

The info block clearly explains what users will encounter during bun prisma init --db, including region selection and database naming. This proactive guidance reduces confusion and improves the setup experience. Placement is spot-on—right after the command that triggers these prompts.

---

126-137: Adapter pattern implementation is clean and consistent.

Both your db.ts and seed.ts correctly instantiate the PrismaPg adapter and pass it to PrismaClient—the right way to use driver adapters. Your schema keeps provider = "postgresql" (correct; the adapter is a client-side concern), and your environment setup now uses a direct postgres:// connection string rather than an Accelerate proxy URL. The migration from Accelerate to driver adapters is complete and systematic throughout this guide. The only potential item worth thinking about: if PrismaClient will be imported in multiple places, consider exporting it from db.ts to avoid duplicating the adapter initialization (as you've done with the export const prisma pattern)—though I see you're already doing this correctly in the seed script import path.

Also applies to: 143-184

content/800-guides/050-migrate-from-mongoose.mdx (1)

17-21: ---

Clarify the warning—the traditional MongoDB connector works in v7; only driver adapters are in progress.

The guide teaches Prisma's traditional MongoDB connector pattern (datasource db { provider = "mongodb" ...}), which is production-ready in both v6 and v7. The current warning suggests v7 support is incomplete, which is misleading.

The distinction matters:

• Traditional MongoDB connector: Fully supported in v7 ✓
• MongoDB driver adapter (new Query Compiler architecture): Still in progress

Since the guide's code examples use the traditional connector, they will work in v7 without modification. Consider updating the warning to clarify this:

"This guide uses the traditional MongoDB connector, which is compatible with Prisma ORM v6 and v7. Note: MongoDB driver adapters for the new Query Compiler are still in progress."

Alternatively, if the guide will eventually migrate to driver adapters, leave the warning but add a link to tracking issues or v7 migration guidance for transparency.

⛔ Skipped due to learnings

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.

[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	2238
✅ Successful	2208
⏳ Timeouts	0
🔀 Redirected	3
👻 Excluded	22
❓ Unknown	0
🚫 Errors	4
⛔ Unsupported	1

Errors per input

Errors in 200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx

• [ERROR] https://nexusjs.org/docs/plugins/prisma/overview | Error (cached)

Errors in 200-orm/100-prisma-schema/20-data-model/30-indexes.mdx

• [503] https://www.postgresql.org/docs/14/brin-builtin-opclasses.html | Rejected status code (this depends on your "accept" configuration): Service Unavailable

Errors in 250-postgres/300-database/525-postgres-extensions.mdx

• [503] https://www.postgresql.org/docs/current/dict-int.html | Rejected status code (this depends on your "accept" configuration): Service Unavailable
• [503] https://www.postgresql.org/docs/current/pgsurgery.html | Rejected status code (this depends on your "accept" configuration): Service Unavailable