docs(postgres): remove accelerate reference #7246
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* `prisma-client-js` deprecated * chore: empty commit * broken link updated
* added env vars section to various pages * minor coderabbit updates * verbose removed * test removed redirect list * removed quickstart addition * converted quickstarts back
* middleware deleted * more middleware removed * more middleware removed * coderabbit changes
Contributor
Dangerous URL checkNo absolute URLs to prisma.io/docs found. |
Contributor
Redirect checkThis PR probably requires the following redirects to be added to static/_redirects: |
Contributor
WalkthroughLarge-scale restructuring of getting-started documentation, moving from an old flat structure to a new organized hierarchy under Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45–60 minutes Areas requiring extra attention:
Possibly related PRs
Pre-merge checks✅ Passed checks (3 passed)
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. Comment |
Contributor
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 76.7%, saving 197.3 KB.
|
Deploying docs with
|
| Latest commit: |
858a231
|
| Status: | 🚫 Build failed. |
Contributor
🍈 Lychee Link Check Report
📊 Results Overview
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
static/img/postgres/connection-string.pngis excluded by!**/*.png
📒 Files selected for processing (12)
content/250-postgres/100-introduction/250-overview.mdx(1 hunks)content/250-postgres/300-database/350-caching.mdx(0 hunks)content/250-postgres/300-database/400-connection-pooling.mdx(1 hunks)content/250-postgres/300-database/550-local-development.mdx(0 hunks)content/250-postgres/300-database/650-direct-connections.mdx(4 hunks)content/250-postgres/300-database/750-serverless-driver.mdx(3 hunks)content/250-postgres/300-database/800-api-reference/100-caching-api.mdx(0 hunks)content/250-postgres/300-database/800-api-reference/200-error-reference.mdx(1 hunks)content/250-postgres/350-integrations/100-netlify.mdx(6 hunks)content/250-postgres/350-integrations/200-vercel.mdx(2 hunks)content/250-postgres/400-query-optimization/100-setup.mdx(1 hunks)content/250-postgres/400-query-optimization/300-recommendations/400-repeated-query.mdx(1 hunks)
💤 Files with no reviewable changes (3)
- content/250-postgres/300-database/350-caching.mdx
- content/250-postgres/300-database/550-local-development.mdx
- content/250-postgres/300-database/800-api-reference/100-caching-api.mdx
🧰 Additional context used
🧠 Learnings (5)
📚 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/250-postgres/300-database/800-api-reference/200-error-reference.mdxcontent/250-postgres/350-integrations/200-vercel.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/300-database/800-api-reference/200-error-reference.mdxcontent/250-postgres/350-integrations/200-vercel.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/250-postgres/400-query-optimization/100-setup.mdxcontent/250-postgres/350-integrations/200-vercel.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/250-postgres/400-query-optimization/100-setup.mdxcontent/250-postgres/100-introduction/250-overview.mdxcontent/250-postgres/350-integrations/200-vercel.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/300-database/750-serverless-driver.mdxcontent/250-postgres/350-integrations/100-netlify.mdxcontent/250-postgres/100-introduction/250-overview.mdxcontent/250-postgres/350-integrations/200-vercel.mdx
🪛 LanguageTool
content/250-postgres/300-database/650-direct-connections.mdx
[grammar] ~50-~50: Ensure spelling is correct
Context: ...gres instance, every request is counted asd a [billable operation](/postgres/introd...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
⏰ 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 (16)
content/250-postgres/300-database/800-api-reference/200-error-reference.mdx (2)
91-91: Accelerate references successfully removed.Lines 91 and 97 correctly update the phrasing to align with the PR objective. The changes from "Prisma Accelerate" to "the project" (line 91) and "Prisma Postgres" (line 97) maintain the instructional clarity while removing outdated product references.
Also applies to: 97-97
60-60: Incomplete Accelerate removal on line 60.Line 60 still contains the phrase "when setting up Accelerate in a platform environment," which contradicts the PR objective to remove Accelerate references. This appears to be an oversight, as the rest of the error section has been properly updated.
Verify whether this reference was intentionally preserved or should be updated. If it should be removed, consider whether the guidance should reference "Prisma Postgres" instead or if the entire phrase requires rewording for the v7 context.
content/250-postgres/300-database/650-direct-connections.mdx (2)
11-11: Verify Accelerate reference aligns with PR objectives.Line 11 still contains a reference and link to Prisma Accelerate (
[Prisma Accelerate](/accelerate/)). The PR objective states "Remove reference to accelerate," but the enriched summary indicates a shift toward an "integrated caching layer."Please confirm whether this reference should be:
- Retained as-is to show that Accelerate powers the integrated layer (repositioning rather than removal)
- Removed entirely to align with a stricter interpretation of "remove reference"
If the reference should be removed, here's the suggested edit:
-Prisma Postgres is the perfect choice for your applications, whether you connect to it via [Prisma ORM](/orm) or any other ORM, database library / tool of your choice. If you use it with Prisma ORM, Prisma Postgres comes with built-in connection pooling, and an integrated caching layer (powered by [Prisma Accelerate](/accelerate/)). +Prisma Postgres is the perfect choice for your applications, whether you connect to it via [Prisma ORM](/orm) or any other ORM, database library / tool of your choice. If you use it with Prisma ORM, Prisma Postgres comes with built-in connection pooling and an integrated caching layer.
21-26: Clear and well-structured connection flow.The simplified steps for obtaining a direct connection string are clearer than before. The reordering logically guides users through: authenticate → generate → optionally configure pooling → copy credentials. The image reference supports the workflow nicely.
content/250-postgres/300-database/750-serverless-driver.mdx (2)
7-7: Clarify Early Access status: remove badge or restore warning.Line 7 retains the
early-access-badgesidebar class, but the Early Access warning block was removed. This is inconsistent. Either:
Remove the badge (if the feature is now GA):
- sidebar_class_name: early-access-badgeRestore the warning block (if it's still in Early Access), or update the frontmatter metadata accordingly.
Which is the correct status for the serverless driver in v7? If it's GA, the badge should be removed.
Also applies to: 4-4
35-35: Add quotes around placeholder values in code examples.The placeholder
YOUR_DATABASE_URLappears unquoted in TypeScript/JavaScript code, which is invalid syntax and could confuse users. Since theppgfunction signature expects a string (line 48:connectionString: string), the placeholder should be wrapped in quotes to show valid, runnable code.Apply this diff to fix all three occurrences:
// Line 35 - const sql = ppg(YOUR_DATABASE_URL); + const sql = ppg("YOUR_DATABASE_URL"); // Line 100 - const sql = ppg(YOUR_DATABASE_URL); + const sql = ppg("YOUR_DATABASE_URL"); // Line 135 - connectionString: YOUR_DATABASE_URL, + connectionString: "YOUR_DATABASE_URL",Also applies to: 100-100, 135-135
⛔ 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.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.content/250-postgres/100-introduction/250-overview.mdx (1)
15-15: Straightforward workflow text simplification. Removing the Accelerate link in favor of plain text aligns with the PR's objective to retire Accelerate references. No concerns here.content/250-postgres/400-query-optimization/300-recommendations/400-repeated-query.mdx (1)
22-28: Clean removal of caching guidance. The removal of the info admonition that linked to caching documentation aligns with the broader PR goal. The remaining "Higher costs" bullet stays relevant and self-explanatory.content/250-postgres/350-integrations/200-vercel.mdx (3)
9-11: Clean simplification to single environment variable. Reducing from multiple environment variables to justDATABASE_URLis appropriate for a managed database service. Clear and focused.
69-79: Well-executed migration toprisma.config.tswithdefineConfig. The new config-based approach is cleaner than schema-based configuration and aligns with Prisma v7 patterns. The use ofenv()helper for loadingDATABASE_URLis the right pattern.
81-97: Solid addition ofpostinstallscript with--no-engine. Generating Prisma Client without the engine binary on deployment is a best practice for managed databases. The explanation about why--no-engineis appropriate for Prisma Postgres is helpful.content/250-postgres/300-database/400-connection-pooling.mdx (2)
9-23: Accurate shift from hard-coded to plan-based connection limits. Replacing the fixed "10 connections" messaging with a plan-based table (Free: 10, Starter: 100, Pro: 500, Business: 1000) correctly reflects the product's pricing model. The note about Starter plan sufficiency with an option to increase is practical and user-friendly.
30-30: Accurate description of automatic pool management. Stating that pooling is "managed automatically" for Prisma Postgres correctly conveys that users don't need manual configuration. Clear and helpful.content/250-postgres/350-integrations/100-netlify.mdx (3)
133-135: Configuration mirrors Vercel integration well. Adding explicitprovider = "prisma-client"and output path keeps the pattern consistent across integration guides. Good cross-file consistency.
225-240: Correct version alignment with Prisma v7. Bumping@prisma/clientandprismato^7.0.0aligns with the PR's objective to update for v7 changes. Appropriate use of caret ranges for patch/minor updates.
164-172: Fix the import path in the example code to match the configured Prisma generator output.The documentation examples contain an inconsistency. The
schema.prismaexample configures the generator output as"../src/generated/prisma", but the subsequentapp/page.jsxexample imports from'../generated/prisma/client.js'—missing thesrc/segment.In a typical Next.js project layout, with
prisma/schema.prismaandapp/page.jsx, the generator output path resolves tosrc/generated/prisma/. The import statement must reflect this. Developers following this tutorial will encounter module resolution failures otherwise.Additionally, the non-null assertion on the
DATABASE_URL(line 170) deserves a brief note: while the Netlify extension populates this, it would be helpful to document this assumption explicitly or show basic error handling for cases where the variable might be undefined.-import { PrismaClient } from '../generated/prisma/client.js'; +import { PrismaClient } from '../src/generated/prisma/client.js';⛔ 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.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.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".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.
Contributor
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 8%, saving 4.8 KB.
|
Contributor
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-typescript-mongodb.mdx
Errors in 200-orm/800-more/600-help-and-troubleshooting/050-dataguide/02-introduction-to-data-types.mdx
|
Contributor
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 200-orm/050-overview/500-databases/840-cockroachdb.mdx
Errors in 200-orm/800-more/600-help-and-troubleshooting/050-dataguide/02-introduction-to-data-types.mdx
|
ankur-arch
reviewed
Nov 11, 2025
ankur-arch
reviewed
Nov 11, 2025
petradonka
reviewed
Nov 12, 2025
Contributor
There was a problem hiding this comment.
If this is the caching API reference, are we moving it over to the Accelerate pages?
petradonka
reviewed
Nov 12, 2025
* feat: add new features * fix: revert links * fix: broken links * fix: broken link
* feat(docs): add youtube embeded link to blog post (#7220) Co-authored-by: Arthur Gamby <arthurgamby@Mac-002.lan> * feat(docs): add quick section to blog after the prompt (#7221) Co-authored-by: Arthur Gamby <arthurgamby@Mac-002.lan> * DC-5242 Astro Better-Auth Guide (#7215) * doc created * nextjs betterauth fixed * guide broken down into manageable steps * image added * Optimised images with calibre/image-actions * image updated * Optimised images with calibre/image-actions * lychee only comments on broken links * config updated * lychee updated based on CR comment * chore: trigger CI checks * ignore gnu * fix: update naming to better-auth DC-6120 * Optimised images with calibre/image-actions * chore: shorten word --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Ankur Datta <64993082+ankur-arch@users.noreply.github.com> * feat: restructure getting started side nav * DC-5841 Removed Linkspector (#7231) * removed linkspector * retrigger * retrigger * retrigger * Update label for Prisma Postgres tab (#7236) * fix: content changes for getting started page (#7216) * fix: content changes for getting started page * fix: add redirects * getting started checkpoint * css styles fixed * updates --------- Co-authored-by: Aidan McAlister <aidankmcalister@gmail.com> Co-authored-by: Aidan McAlister <105178005+aidankmcalister@users.noreply.github.com> * DC-5820 AI Agents Served Markdown (#7237) * ai crawler check successful * ai crawlers checked * update * added anthropic * middleware update * improve detection --------- Co-authored-by: Mike Hartington <mikehartington@gmail.com> * feat: add prisma-orm quickstarts * fix: update times and add proper links * fix: instropspect changes * feat: add get started from prisma orm page * feat: add other orms * fix: update other tools + ppg * fix: add more clarity * fix: add prisma postgres * feat: clear migrate from early access * fix: add to existing dbs sections * Remove MCP server exploration tip (#7241) Removed tip about using Cloudflare's AI Playground for MCP server exploration, as it no longer seems to reliably work. * fix: clean-up docs files * fix: typeorm missing urls * fix: broken link * fix: update titles * fix: clear redirect loop (#7250) * fix: add generate step + sqlite fixes * fix: clean-up redirects file DC-6228 * fix: clean-up unnecessary file * fix: remove unknown word * fix: add links --------- Co-authored-by: Arthur <arthur_gamby@hotmail.fr> Co-authored-by: Arthur Gamby <arthurgamby@Mac-002.lan> Co-authored-by: Aidan McAlister <105178005+aidankmcalister@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Petra Donka <donkapetra@gmail.com> Co-authored-by: Aidan McAlister <aidankmcalister@gmail.com> Co-authored-by: Mike Hartington <mikehartington@gmail.com>
* update * use pg adapter instead of accelerate * update * add dotenv in prisma.config.ts * fix warning note * update * update
* (feat) Update guides to use prisma.config.ts * refactor: Updated guides for Prisma 7 changes --------- Co-authored-by: Aman Varshney <amanvarshney.work@gmail.com>
* feat: add kysley * feat: add drizzle * feat: add typeorm * fix: clean-up * feat: separate the sections better * fix: remove badges
* feat: add kysley * feat: add drizzle * feat: add typeorm * fix: clean-up * fix: update prisma init command changes * feat: update prisma cli docs * fix: clarify the usage of prisma init better * fix: add type defs * feat: add pg as a dependency * fix: broken internal link
* feat: add mentions of new Prisma Studio * feat: add note for Studio for SQLite * Update content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx * Update content/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdx * fix: make prisma studio docs more accurate * fix: add missing punctuation
* feat: add mention of mongo support coming for mongo * fix: refinements * Update content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
Contributor
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
content/250-postgres/350-integrations/100-netlify.mdx (1)
164-172: Remove unuseddatabaseUrlvariable.Line 168 declares
databaseUrlbut it's never used—the adapter correctly referencesprocess.env.DATABASE_URLdirectly at line 170. This appears to be a leftover from refactoring. Remove the unused variable to keep the example clean.-const databaseUrl = process.env.DATABASE_URL; const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL!, });
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
content/250-postgres/350-integrations/100-netlify.mdx(7 hunks)content/250-postgres/350-integrations/200-vercel.mdx(3 hunks)content/250-postgres/400-query-optimization/100-setup.mdx(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- content/250-postgres/350-integrations/200-vercel.mdx
🧰 Additional context used
🧠 Learnings (4)
📓 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-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/100-netlify.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/250-postgres/350-integrations/100-netlify.mdxcontent/250-postgres/400-query-optimization/100-setup.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/250-postgres/400-query-optimization/100-setup.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). (1)
- GitHub Check: Cloudflare Pages
🔇 Additional comments (5)
content/250-postgres/400-query-optimization/100-setup.mdx (1)
55-60: ✅ Previous critical issue is now resolved.The dangling
.$extends(withAccelerate())call from the previous commit has been properly removed. The PrismaClient now cleanly extends with onlywithOptimize, and the import statement correctly references only the Optimize extension. The removal of the Accelerate reference aligns with the PR's core objective.content/250-postgres/350-integrations/100-netlify.mdx (4)
50-62: ✅ prisma.config.ts pattern is correct for Prisma v7.The migration from schema-based configuration to
defineConfigwith environment variable wiring is well-executed. The use ofenv('DATABASE_URL')and the explicit schema and output paths align with current Prisma v7 best practices.
132-135: ✅ Generator configuration correctly updated to v7 patterns.The generator provider change from
"prisma-client-js"to"prisma-client"with explicitoutputpath is the correct v7 approach. This matches the postinstall script update (prisma generate) and removal of the deprecated--no-engineflag from line 74.
164-172: PrismaPg adapter integration looks correct for Prisma v7.The adapter pattern—creating a
PrismaPginstance withconnectionStringand passing it toPrismaClient—is the proper v7 approach. All Accelerate references have been cleanly removed, and the runtime now relies on direct database connection through the adapter instead of a caching/acceleration layer.
225-225: ✅ Prisma package versions correctly bumped to v7.Both
@prisma/client(line 225) andprismadevDependency (line 240) are pinned to^7.0.0, which aligns with the PR's objective to modernize the documentation for Prisma v7. The new adapter-pg dependency would also need to be added todependenciesordevDependenciesfor this example to work, but that's not visible in the provided snippet—verify it's included elsewhere in the file or in a separate dependency section.Is the
@prisma/adapter-pgpackage listed in thedependenciessection of this example'spackage.json?Also applies to: 240-240
Remove reference to accelerate and rework the docs to account for the new v7 changes
mhartington
force-pushed
the
ppg-no-accelerate
branch
from
982dacf to
83013e4
Compare
Contributor
🍈 Lychee Link Check Report
📊 Results Overview
|
aidankmcalister
force-pushed
the
prisma-7
branch
from
d68abc3 to
e92f2a3
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (15)
content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx (2)
4-4: Align metaTitle with the title's sentence case pattern.The
metaTitleuses "Quickstart: Prisma ORM with MySQL" while the page title uses "Quickstart with Prisma ORM and MySQL". For consistency and to follow sentence case conventions, update the metaTitle to match the title pattern.- metaTitle: 'Quickstart: Prisma ORM with MySQL (10 min)' + metaTitle: 'Quickstart with Prisma ORM and MySQL (10 min)'Also applies to: 4-4
21-21: Add section numbering to Prerequisites for consistency.The subsequent sections are all numbered (## 2., ## 3., ... ## 9.), but the Prerequisites section lacks a number. To maintain a consistent numbered structure throughout the quickstart, renumber this section as the first step.
- ## Prerequisites + ## 1. PrerequisitesAlso applies to: 23-23
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdx (1)
210-248: Strengthen wording in section heading.The phrasing "To make changes to your database schema:" followed by a subsection is slightly awkward. Consider restructuring this for clarity. For example, you could retitle section 9 to "Evolve your schema with Prisma Migrate" or simply move directly to subsection 9.1 without the introductory line.
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdx (2)
237-237: Inconsistent subsection heading format.The subsection at line 237 ends with a colon (
### 9.2. Create and apply a migration:), while the previous subsection at line 213 does not (### 9.1. Update your Prisma schema file). For consistency, remove the trailing colon to match the style of the first subsection.-### 9.2. Create and apply a migration: +### 9.2. Create and apply a migration
211-211: Consider strengthening the introductory wording.The line "To make changes to your database schema:" is somewhat indirect. You could strengthen it to be more action-oriented. Per static analysis, consider rephrasing for better clarity.
For example, you might say something like: "Update your schema and create a migration" to be more direct about what this section covers.
.github/workflows/lychee.yml (1)
36-36: Clarify the rationale for excluding gnu.org from link checks.The workflow now excludes
https://www.gnu.orgfrom both Lychee runs. Is this domain:
- Frequently unreachable or rate-limiting in your docs?
- Not relevant to the Prisma docs content?
- Known to have false positives?
Adding context to the code or a comment would help future maintainers understand this decision.
Consider adding an inline comment explaining why gnu.org is excluded:
--exclude 'https://www.gnu.org' + # Exclude gnu.org due to [reason: rate limiting | not applicable | etc.]Also applies to: 62-62
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdx (1)
191-217: Address wordy phrasing in schema evolution section.The static analysis tool flagged line 193 as potentially wordy: "To make changes to your database schema:" could be more concise.
Consider shortening the introductory text:
- To make changes to your database schema: + To evolve your schema:This is minor, but sharpens the language per static analysis feedback.
content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx (3)
14-20: Tighten the wordy phrasing in the MongoDB v7 warning.The static analysis tool flagged "In the meantime, please use" as potentially wordy. Consider revising:
- **MongoDB support for Prisma ORM v7 is coming in the near future.** In the meantime, please use **Prisma ORM v6.19** (the latest v6 release) when working with MongoDB. + **MongoDB support for Prisma ORM v7 is coming soon.** For now, use **Prisma ORM v6.19** (the latest v6 release) when working with MongoDB.This tightens the language without losing clarity.
28-34: Simplify verbose prerequisite intro language.The static analysis tool flagged "In order to successfully complete this guide, you need:" as wordy. Consider:
- In order to successfully complete this guide, you need: + To complete this guide, you need:This maintains clarity while being more concise.
158-165: Standardize "username" as one word.The static analysis tool recommended using "username" (one word) instead of "user name" for technical contexts. Update line 160:
- **`USERNAME`**: Your database user name + **`USERNAME`**: Your database usernamecontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdx (1)
210-217: Address wordy phrasing in schema evolution section.Similar to the PlanetScale guide, line 212 contains wordy phrasing flagged by static analysis: "To make changes to your database schema:" could be more direct.
Consider:
- To make changes to your database schema: + To evolve your schema:This matches the recommended style from the static analysis feedback.
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx (3)
14-20: Tighten the wordy phrasing in the MongoDB v7 warning.Static analysis flagged "In the meantime, please use" as potentially verbose. Revise to:
- **MongoDB support for Prisma ORM v7 is coming in the near future.** In the meantime, please use **Prisma ORM v6.19** (the latest v6 release) when working with MongoDB. + **MongoDB support for Prisma ORM v7 is coming soon.** For now, use **Prisma ORM v6.19** (the latest v6 release) when working with MongoDB.
28-34: Simplify verbose prerequisite intro language.Static analysis flagged "In order to successfully complete this guide, you need:" as wordy. Consider:
- In order to successfully complete this guide, you need: + To complete this guide, you need:
158-165: Standardize "username" as one word.Static analysis recommended "username" (one word) for technical contexts. Update line 160:
- **`USERNAME`**: Your database user name + **`USERNAME`**: Your database usernamecontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdx (1)
206-209: Minor wording tightening opportunity.The phrase "To make changes to your database schema:" at line 208 could be more direct. Consider: "To evolve your database schema:" or simply "Update your Prisma schema file:" to strengthen the action orientation.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (107)
.github/workflows/config/.linkspector.yml(0 hunks).github/workflows/linkspector.yml(0 hunks).github/workflows/lychee.yml(4 hunks)cSpell.json(2 hunks)content/100-getting-started/01-quickstart-prismaPostgres.mdx(0 hunks)content/100-getting-started/01-quickstart-sqlite.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx(1 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx(1 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdx(1 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx(1 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdx(1 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdx(1 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdx(1 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx(1 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdx(1 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdx(1 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdx(1 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/400-mysql.mdx(1 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/500-sql-server.mdx(1 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdx(1 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdx(1 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx(1 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-prismaPostgres.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-prismaPostgres.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-prismaPostgres.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-prismaPostgres.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-prismaPostgres.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/300-next-steps.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/_install-prisma-client-partial.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/300-next-steps.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/_prisma-init-partial.mdx(0 hunks)content/100-getting-started/02-setup-prisma/100-start-from-scratch/index.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-sqlserver.mdx(0 hunks)
⛔ Files not processed due to max files limit (70)
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/300-next-steps.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/_install-prisma-client-partial.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-typescript-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-typescript-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-typescript-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-typescript-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/300-next-steps.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/_prisma-init-partial.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/index.mdx
- content/100-getting-started/02-setup-prisma/index.mdx
- content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx
- content/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx
- content/100-getting-started/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdx
💤 Files with no reviewable changes (89)
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-prismaPostgres.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/300-next-steps.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-typescript-mongodb.mdx
- content/100-getting-started/01-quickstart-sqlite.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-prismaPostgres.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/_install-prisma-client-partial.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/300-next-steps.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-typescript-mongodb.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-prismaPostgres.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-prismaPostgres.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/index.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx
- .github/workflows/config/.linkspector.yml
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-typescript-mongodb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-prismaPostgres.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-cockroachdb.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/_prisma-init-partial.mdx
- .github/workflows/linkspector.yml
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-postgresql.mdx
- content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-mysql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx
- content/100-getting-started/01-quickstart-prismaPostgres.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-cockroachdb.mdx
✅ Files skipped from review due to trivial changes (1)
- content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx
🧰 Additional context used
🧠 Learnings (7)
📓 Common 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: 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".
📚 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/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/400-mysql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/500-sql-server.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.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/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/400-mysql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/500-sql-server.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.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/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/400-mysql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/500-sql-server.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.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/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/400-mysql.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.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/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.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/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdx
🪛 LanguageTool
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdx
[style] ~212-~212: Consider shortening or rephrasing this to strengthen your wording.
Context: ...pt.ts ``` ## 9. Evolve your schema To make changes to your database schema: ### 9.1. Update ...
(MAKE_CHANGES)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdx
[style] ~193-~193: Consider shortening or rephrasing this to strengthen your wording.
Context: ...w instead of traditional migrations. To make changes to your database schema: ### 8.1. Update ...
(MAKE_CHANGES)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
[style] ~16-~16: ‘In the meantime’ might be wordy. Consider a shorter alternative.
Context: ... ORM v7 is coming in the near future.** In the meantime, please use Prisma ORM v6.19 (the l...
(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)
[style] ~29-~29: Consider a more concise word here.
Context: ...from-mongoose). ::: ## Prerequisites In order to successfully complete this guide, you n...
(IN_ORDER_TO_PREMIUM)
[style] ~160-~160: It’s more common nowadays to write this noun as one word.
Context: ...nents: - USERNAME: Your database user name - PASSWORD: Your database user pa...
(RECOMMENDED_COMPOUNDS)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/400-mysql.mdx
[style] ~221-~221: Consider shortening or rephrasing this to strengthen your wording.
Context: ...pt.ts ``` ## 9. Evolve your schema To make changes to your database schema: ### 9.1. Update ...
(MAKE_CHANGES)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/500-sql-server.mdx
[style] ~232-~232: Consider shortening or rephrasing this to strengthen your wording.
Context: ...pt.ts ``` ## 9. Evolve your schema To make changes to your database schema: ### 9.1. Update ...
(MAKE_CHANGES)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdx
[style] ~208-~208: Consider shortening or rephrasing this to strengthen your wording.
Context: ...pt.ts ``` ## 9. Evolve your schema To make changes to your database schema: ### 9.1. Update ...
(MAKE_CHANGES)
content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
[style] ~17-~17: ‘In the meantime’ might be wordy. Consider a shorter alternative.
Context: ... ORM v7 is coming in the near future.** In the meantime, please use Prisma ORM v6.19 (the l...
(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdx
[style] ~211-~211: Consider shortening or rephrasing this to strengthen your wording.
Context: ...pt.ts ``` ## 9. Evolve your schema To make changes to your database schema: ### 9.1. Update ...
(MAKE_CHANGES)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdx
[style] ~212-~212: Consider shortening or rephrasing this to strengthen your wording.
Context: ...pt.ts ``` ## 9. Evolve your schema To make changes to your database schema: ### 9.1. Update ...
(MAKE_CHANGES)
⏰ 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove reference to accelerate and rework the docs to account for the new v7 changes
Summary by CodeRabbit
Documentation
Chores