Update ORM docs #7260
Open
Update ORM docs #7260
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
Contributor
|
Warning Rate limit exceeded@AmanVarshney01 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 43 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
WalkthroughDocumentation-wide edits: generator provider examples switched from "prisma-client-js" → "prisma-client" with explicit output="./generated"; datasource URL examples removed from schema and new prisma.config.ts examples added; Prisma Client import paths in examples updated to generated-client locations; Admonition markup converted to MDX directive syntax. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Areas to pay extra attention:
Possibly related PRs
Pre-merge checks❌ Failed checks (1 inconclusive)
✅ Passed checks (2 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
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
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx
Errors in 200-orm/800-more/400-comparisons/04-prisma-and-drizzle.mdx
|
Deploying docs with
|
| Latest commit: |
82c4772
|
| Status: | 🚫 Build failed. |
![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: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (11)
content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx (1)
517-524: Update generator provider to match PR standardization.This MongoDB example in the
@@fulltextsection still uses the outdatedprisma-client-jsprovider, which is inconsistent with the PR's goal to standardize all examples on the newprisma-clientprovider with explicit output paths.Apply this diff to align with the rest of the documentation:
generator js { - provider = "prisma-client-js" + provider = "prisma-client" + output = "./generated" previewFeatures = ["fullTextIndex"] }content/200-orm/050-overview/500-databases/890-neon.mdx (2)
61-67: Schema snippet is missing the promised directUrl line.The text says “update your schema.prisma to use the new direct URL” but the snippet only shows provider. Add the directUrl line or adjust wording to match Prisma Config usage.
Apply this diff if you intend to keep it in the schema:
datasource db { provider = "postgresql" + directUrl = env("DIRECT_URL") }
120-124: Fix typo: “istall” → “install”.“…istall the Prisma ORM adapter…” should be “…install the Prisma ORM adapter…”.
content/200-orm/500-reference/100-prisma-schema-reference.mdx (2)
27-29: Admonition syntax is malformed.Use triple-colon blocks. Replace “::::note … ::::” with a proper block:
:::note As of Prisma ORM v7, the `url`, `directUrl`, and `shadowDatabaseUrl` fields … :::
171-179: Field listed under wrong generator.
moduleFormatis documented here under the prisma-client-js table but the description says “available only withprisma-clientgenerator.” Move it to theprisma-clientsection or clarify availability.content/200-orm/050-overview/500-databases/800-sql-server/index.mdx (1)
51-54: Incorrect driver attribution.“For SQLite,
node-mssqlis one of the most popular drivers…” should be “For SQL Server,node-mssql…”.Apply this diff:
-For SQLite, [`node-mssql`](https://github.com/tediousjs/node-mssql) is one of the most popular drivers in the JavaScript ecosystem. +For SQL Server, [`node-mssql`](https://github.com/tediousjs/node-mssql) is one of the most popular drivers in the JavaScript ecosystem.content/200-orm/050-overview/500-databases/200-database-drivers.mdx (3)
15-16: Version text/link mismatch.“As of v6.15.0” links to the v6.16.0 release. Align the text with the link (likely v6.16.0).
21-25: Unify generator output path across page.You use
output = "../src/generated/prisma"earlier andoutput = "../src/generated/client"later. Standardize to one path to prevent reader confusion.Also applies to: 156-160
123-124: Import path likely incorrect.
import { PrismaClient } from '../prisma/prisma-client'doesn’t match the earlier configured output. Use the same generated client path (or the linked dependency name) shown elsewhere on the page.Apply one of:
-import { PrismaClient } from '../prisma/prisma-client' +import { PrismaClient } from '../prisma/generated/client'or, if using a linked dependency per the section below:
-import { PrismaClient } from '../prisma/prisma-client' +import { PrismaClient } from 'db'content/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdx (1)
240-241: Fix typo: “re-dployment” → “re-deployment”.“…to trigger a re-dployment.” → “…to trigger a re-deployment.”
content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx (1)
594-602: Align import path to documented conventionThis documentation example deviates from the established pattern used throughout the codebase. The suggested import path
../prisma/generated/clientmatches the standard convention documented in 20+ other documentation files, including prisma-cli-reference.mdx, nuxt-module.mdx, and github-copilot.mdx. The current./generated/clientpath only appears in this single example, making it an outlier that could confuse developers following the guides.- import { PrismaClient } from './generated/client' + import { PrismaClient } from '../prisma/generated/client'
🧹 Nitpick comments (8)
content/200-orm/100-prisma-schema/20-data-model/40-views.mdx (1)
31-38: Update highlighting directive to match documentation patterns.The addition of
output = "./generated"correctly aligns with the PR objectives to standardize generator configuration with explicit output paths. However, the//add-next-linecomment on line 35 appears redundant—the code block already controls highlighting viahighlight=3;addin the attributes. Other examples in this file (lines 194–202, 208–216) use//highlight-startand//highlight-endfor inline highlighting, suggesting this comment may be unnecessary or a leftover from the migration.Consider removing the
//add-next-linecomment to keep the directive clean:```prisma file=schema.prisma highlight=3;add showLineNumbers generator client { provider = "prisma-client" output = "./generated" - //add-next-line previewFeatures = ["views"] }</blockquote></details> <details> <summary>content/200-orm/200-prisma-client/100-queries/061-custom-validation.mdx (1)</summary><blockquote> `22-26`: **Minor: Grammar—hyphenate compound adjective** Line 24: "top level data object" should be "top-level data object" to properly hyphenate the compound modifier. </blockquote></details> <details> <summary>content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx (1)</summary><blockquote> `897-899`: **Minor: Grammar—prefer "cannot" over "can not"** Line 897: Change "you can not use" to "you cannot use" for standard English grammar. </blockquote></details> <details> <summary>content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx (1)</summary><blockquote> `157-161`: **Note on optional wording improvement.** The static analysis tool suggests shortening line 165 from "Whenever you make changes..." to improve directness, though the current phrasing is acceptable. Consider: "Make changes to your database that are reflected in the Prisma schema to re-generate Prisma Client." </blockquote></details> <details> <summary>content/200-orm/200-prisma-client/100-queries/030-crud.mdx (1)</summary><blockquote> `263-267`: **Terminology improvement: Consider standardizing "SQL Server" naming.** Line 265 contains the phrase `"MongoDB, SQLServer, or SQLite"`. Microsoft's official product name is "SQL Server" (two words), not "SQLServer". While this appears to be pre-existing text, standardizing it to "SQL Server" would improve accuracy and align with official documentation conventions. This is a minor terminology refinement; if you're open to it, updating this to use the official "SQL Server" name would be a nice polish: ```diff -Note `skipDuplicates` is not supported when using MongoDB, SQLServer, or SQLite. +Note `skipDuplicates` is not supported when using MongoDB, SQL Server, or SQLite.content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx (1)
276-280: EngineType “client”: nice inclusion.The generator example for no-Rust setup is accurate and aligns with driver-adapter guidance. Consider linking to the same “no Rust engine” page referenced earlier in this doc for continuity.
content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx (1)
108-126: Nice addition of Prisma Config section. One follow-up for consistency.Since this page now positions Prisma Config as the place for URLs, consider updating the MongoDB tab’s datasource example above to remove
url = env("DATABASE_URL")(or add a note clarifying legacy vs. new configuration).Please confirm whether MongoDB examples should also move URL config to Prisma Config on the prisma-7 branch.
content/200-orm/500-reference/050-prisma-client-reference.mdx (1)
110-110: Clarify import path assumptions vs output folderSamples import from ../prisma/generated/client while earlier examples set output = "./generated". Both are valid depending on project layout, but mixing them in one page can confuse readers. Add a short note stating: “In this page, imports assume the client is generated to prisma/generated/client relative to project root; adjust paths to match your output.”
Also applies to: 142-142, 211-211, 250-250, 299-299, 418-418, 715-715, 851-851, 5601-5601, 5619-5619
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (107)
content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx(5 hunks)content/200-orm/050-overview/100-introduction/300-data-modeling.mdx(1 hunks)content/200-orm/050-overview/300-prisma-in-your-stack/01-rest.mdx(1 hunks)content/200-orm/050-overview/300-prisma-in-your-stack/03-fullstack.mdx(1 hunks)content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx(4 hunks)content/200-orm/050-overview/500-databases/200-database-drivers.mdx(4 hunks)content/200-orm/050-overview/500-databases/300-postgresql.mdx(3 hunks)content/200-orm/050-overview/500-databases/400-mysql.mdx(2 hunks)content/200-orm/050-overview/500-databases/500-sqlite.mdx(2 hunks)content/200-orm/050-overview/500-databases/600-mongodb.mdx(4 hunks)content/200-orm/050-overview/500-databases/800-sql-server/index.mdx(4 hunks)content/200-orm/050-overview/500-databases/840-cockroachdb.mdx(2 hunks)content/200-orm/050-overview/500-databases/850-planetscale.mdx(5 hunks)content/200-orm/050-overview/500-databases/880-supabase.mdx(1 hunks)content/200-orm/050-overview/500-databases/890-neon.mdx(2 hunks)content/200-orm/050-overview/500-databases/900-turso.mdx(1 hunks)content/200-orm/050-overview/600-beyond-prisma-orm.mdx(1 hunks)content/200-orm/100-prisma-schema/10-overview/index.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/10-models.mdx(10 hunks)content/200-orm/100-prisma-schema/20-data-model/20-relations/100-one-to-one-relations.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/20-relations/200-one-to-many-relations.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/20-relations/300-many-to-many-relations.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx(8 hunks)content/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdx(4 hunks)content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx(5 hunks)content/200-orm/100-prisma-schema/20-data-model/40-views.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/50-database-mapping.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/65-externally-managed-tables.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdx(1 hunks)content/200-orm/100-prisma-schema/20-data-model/80-table-inheritance.mdx(3 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx(2 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx(5 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/015-instantiate-prisma-client.mdx(2 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/100-connection-management.mdx(2 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx(5 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx(5 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/200-read-replicas.mdx(1 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdx(12 hunks)content/200-orm/200-prisma-client/100-queries/030-crud.mdx(5 hunks)content/200-orm/200-prisma-client/100-queries/037-relation-queries.mdx(1 hunks)content/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdx(2 hunks)content/200-orm/200-prisma-client/100-queries/056-aggregation-grouping-summarizing.mdx(2 hunks)content/200-orm/200-prisma-client/100-queries/058-transactions.mdx(9 hunks)content/200-orm/200-prisma-client/100-queries/060-full-text-search.mdx(3 hunks)content/200-orm/200-prisma-client/100-queries/061-custom-validation.mdx(2 hunks)content/200-orm/200-prisma-client/100-queries/062-computed-fields.mdx(2 hunks)content/200-orm/200-prisma-client/100-queries/064-custom-models.mdx(2 hunks)content/200-orm/200-prisma-client/100-queries/070-case-sensitivity.mdx(1 hunks)content/200-orm/200-prisma-client/150-using-raw-sql/100-typedsql.mdx(1 hunks)content/200-orm/200-prisma-client/150-using-raw-sql/200-raw-queries.mdx(5 hunks)content/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdx(2 hunks)content/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdx(4 hunks)content/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdx(2 hunks)content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx(7 hunks)content/200-orm/200-prisma-client/200-special-fields-and-types/200-working-with-scalar-lists-arrays.mdx(4 hunks)content/200-orm/200-prisma-client/200-special-fields-and-types/300-working-with-composite-ids-and-constraints.mdx(2 hunks)content/200-orm/200-prisma-client/300-client-extensions/100-model.mdx(2 hunks)content/200-orm/200-prisma-client/300-client-extensions/110-client.mdx(2 hunks)content/200-orm/200-prisma-client/300-client-extensions/120-query.mdx(2 hunks)content/200-orm/200-prisma-client/300-client-extensions/130-result.mdx(1 hunks)content/200-orm/200-prisma-client/300-client-extensions/index.mdx(1 hunks)content/200-orm/200-prisma-client/400-type-safety/830-prisma-type-system.mdx(0 hunks)content/200-orm/200-prisma-client/400-type-safety/index.mdx(1 hunks)content/200-orm/200-prisma-client/450-testing/100-unit-testing.mdx(1 hunks)content/200-orm/200-prisma-client/450-testing/150-integration-testing.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx(1 hunks)content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx(8 hunks)content/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdx(9 hunks)content/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdx(5 hunks)content/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdx(1 hunks)content/200-orm/200-prisma-client/600-observability-and-logging/130-logging.mdx(1 hunks)content/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx(4 hunks)content/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdx(3 hunks)content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/140-debugging.mdx(1 hunks)content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx(1 hunks)content/200-orm/300-prisma-migrate/050-getting-started.mdx(0 hunks)content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/005-overview.mdx(1 hunks)content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdx(1 hunks)content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx(4 hunks)content/200-orm/300-prisma-migrate/300-workflows/110-native-database-types.mdx(1 hunks)content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx(1 hunks)content/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdx(2 hunks)content/200-orm/300-prisma-migrate/300-workflows/200-troubleshooting.mdx(1 hunks)content/200-orm/300-prisma-migrate/300-workflows/30-baselining.mdx(1 hunks)content/200-orm/300-prisma-migrate/300-workflows/40-customizing-migrations.mdx(1 hunks)content/200-orm/300-prisma-migrate/300-workflows/50-squashing-migrations.mdx(3 hunks)content/200-orm/300-prisma-migrate/300-workflows/60-generating-down-migrations.mdx(1 hunks)content/200-orm/300-prisma-migrate/300-workflows/70-patching-and-hotfixing.mdx(2 hunks)content/200-orm/300-prisma-migrate/300-workflows/80-unsupported-database-features.mdx(1 hunks)content/200-orm/300-prisma-migrate/300-workflows/90-development-and-production.mdx(2 hunks)content/200-orm/500-reference/050-prisma-client-reference.mdx(30 hunks)content/200-orm/500-reference/100-prisma-schema-reference.mdx(15 hunks)content/200-orm/500-reference/200-prisma-cli-reference.mdx(21 hunks)content/200-orm/500-reference/250-error-reference.mdx(1 hunks)content/200-orm/500-reference/300-environment-variables-reference.mdx(4 hunks)content/200-orm/500-reference/325-prisma-config-reference.mdx(1 hunks)content/200-orm/500-reference/380-connection-urls.mdx(0 hunks)content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx(1 hunks)content/200-orm/800-more/100-under-the-hood/100-engines.mdx(3 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/101-jsonprotocol-changes.mdx(1 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdx(3 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdx(1 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/150-referential-actions.mdx(2 hunks)content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/index.mdx(2 hunks)
⛔ Files not processed due to max files limit (17)
- content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/900-codemods.mdx
- content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/index.mdx
- content/200-orm/800-more/300-upgrade-guides/250-upgrading-to-use-preview-features.mdx
- content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/08-upgrade-from-mongodb-beta.mdx
- content/200-orm/800-more/350-ai-tools/100-cursor.mdx
- content/200-orm/800-more/350-ai-tools/200-tabnine.mdx
- content/200-orm/800-more/350-ai-tools/300-windsurf.mdx
- content/200-orm/800-more/350-ai-tools/400-github-copilot.mdx
- content/200-orm/800-more/600-help-and-troubleshooting/100-autocompletion-in-graphql-resolvers-with-js.mdx
- content/200-orm/800-more/600-help-and-troubleshooting/300-implicit-to-explicit-conversion.mdx
- content/200-orm/800-more/600-help-and-troubleshooting/400-nextjs-help.mdx
- content/200-orm/800-more/600-help-and-troubleshooting/500-comparing-columns-through-raw-queries.mdx
- content/200-orm/800-more/600-help-and-troubleshooting/600-vercel-caching-issue.mdx
- content/200-orm/800-more/600-help-and-troubleshooting/700-netlify-caching-issue.mdx
- content/200-orm/800-more/600-help-and-troubleshooting/800-check-constraints.mdx
- content/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdx
- content/200-orm/800-more/600-help-and-troubleshooting/950-typescript-performance-optimization.mdx
💤 Files with no reviewable changes (3)
- content/200-orm/500-reference/380-connection-urls.mdx
- content/200-orm/200-prisma-client/400-type-safety/830-prisma-type-system.mdx
- content/200-orm/300-prisma-migrate/050-getting-started.mdx
🧰 Additional context used
🧠 Learnings (9)
📓 Common learnings
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.
Learnt from: 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: 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.
📚 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/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdxcontent/200-orm/200-prisma-client/300-client-extensions/110-client.mdxcontent/200-orm/200-prisma-client/300-client-extensions/index.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/100-connection-management.mdxcontent/200-orm/300-prisma-migrate/300-workflows/60-generating-down-migrations.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdxcontent/200-orm/200-prisma-client/450-testing/100-unit-testing.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/index.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/200-working-with-scalar-lists-arrays.mdxcontent/200-orm/200-prisma-client/300-client-extensions/100-model.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/101-jsonprotocol-changes.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/130-logging.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/300-working-with-composite-ids-and-constraints.mdxcontent/200-orm/200-prisma-client/300-client-extensions/120-query.mdxcontent/200-orm/200-prisma-client/100-queries/061-custom-validation.mdxcontent/200-orm/200-prisma-client/100-queries/056-aggregation-grouping-summarizing.mdxcontent/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdxcontent/200-orm/800-more/100-under-the-hood/100-engines.mdxcontent/200-orm/200-prisma-client/700-debugging-and-troubleshooting/140-debugging.mdxcontent/200-orm/200-prisma-client/400-type-safety/index.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/150-referential-actions.mdxcontent/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdxcontent/200-orm/300-prisma-migrate/300-workflows/70-patching-and-hotfixing.mdxcontent/200-orm/300-prisma-migrate/300-workflows/40-customizing-migrations.mdxcontent/200-orm/300-prisma-migrate/300-workflows/90-development-and-production.mdxcontent/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdxcontent/200-orm/300-prisma-migrate/300-workflows/50-squashing-migrations.mdxcontent/200-orm/100-prisma-schema/20-data-model/30-indexes.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/200-prisma-client/100-queries/070-case-sensitivity.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/100-prisma-schema/20-data-model/10-models.mdxcontent/200-orm/050-overview/100-introduction/100-what-is-prisma.mdxcontent/200-orm/200-prisma-client/450-testing/150-integration-testing.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdxcontent/200-orm/200-prisma-client/100-queries/060-full-text-search.mdxcontent/200-orm/300-prisma-migrate/300-workflows/110-native-database-types.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/100-one-to-one-relations.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/300-many-to-many-relations.mdxcontent/200-orm/500-reference/325-prisma-config-reference.mdxcontent/200-orm/300-prisma-migrate/300-workflows/30-baselining.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/200-raw-queries.mdxcontent/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdxcontent/200-orm/050-overview/500-databases/880-supabase.mdxcontent/200-orm/500-reference/250-error-reference.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/100-typedsql.mdxcontent/200-orm/100-prisma-schema/20-data-model/50-database-mapping.mdxcontent/200-orm/300-prisma-migrate/300-workflows/80-unsupported-database-features.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdxcontent/200-orm/200-prisma-client/300-client-extensions/130-result.mdxcontent/200-orm/300-prisma-migrate/300-workflows/200-troubleshooting.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdxcontent/200-orm/050-overview/500-databases/600-mongodb.mdxcontent/200-orm/050-overview/600-beyond-prisma-orm.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdxcontent/200-orm/200-prisma-client/100-queries/058-transactions.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/005-overview.mdxcontent/200-orm/100-prisma-schema/10-overview/index.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdxcontent/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdxcontent/200-orm/050-overview/500-databases/300-postgresql.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdxcontent/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdxcontent/200-orm/050-overview/500-databases/840-cockroachdb.mdxcontent/200-orm/500-reference/200-prisma-cli-reference.mdxcontent/200-orm/500-reference/050-prisma-client-reference.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdxcontent/200-orm/050-overview/500-databases/800-sql-server/index.mdxcontent/200-orm/050-overview/500-databases/890-neon.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdxcontent/200-orm/050-overview/500-databases/400-mysql.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/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdxcontent/200-orm/200-prisma-client/300-client-extensions/110-client.mdxcontent/200-orm/200-prisma-client/300-client-extensions/index.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/100-connection-management.mdxcontent/200-orm/300-prisma-migrate/300-workflows/60-generating-down-migrations.mdxcontent/200-orm/200-prisma-client/450-testing/100-unit-testing.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/index.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/200-working-with-scalar-lists-arrays.mdxcontent/200-orm/200-prisma-client/300-client-extensions/100-model.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/130-logging.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/200-one-to-many-relations.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/300-working-with-composite-ids-and-constraints.mdxcontent/200-orm/200-prisma-client/300-client-extensions/120-query.mdxcontent/200-orm/200-prisma-client/100-queries/061-custom-validation.mdxcontent/200-orm/200-prisma-client/100-queries/056-aggregation-grouping-summarizing.mdxcontent/200-orm/800-more/100-under-the-hood/100-engines.mdxcontent/200-orm/200-prisma-client/700-debugging-and-troubleshooting/140-debugging.mdxcontent/200-orm/200-prisma-client/400-type-safety/index.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/150-referential-actions.mdxcontent/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdxcontent/200-orm/300-prisma-migrate/300-workflows/70-patching-and-hotfixing.mdxcontent/200-orm/300-prisma-migrate/300-workflows/40-customizing-migrations.mdxcontent/200-orm/300-prisma-migrate/300-workflows/90-development-and-production.mdxcontent/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdxcontent/200-orm/200-prisma-client/100-queries/062-computed-fields.mdxcontent/200-orm/200-prisma-client/100-queries/064-custom-models.mdxcontent/200-orm/300-prisma-migrate/300-workflows/50-squashing-migrations.mdxcontent/200-orm/100-prisma-schema/20-data-model/30-indexes.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/200-prisma-client/100-queries/070-case-sensitivity.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/200-prisma-client/450-testing/150-integration-testing.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdxcontent/200-orm/200-prisma-client/100-queries/060-full-text-search.mdxcontent/200-orm/300-prisma-migrate/300-workflows/110-native-database-types.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/100-one-to-one-relations.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/300-many-to-many-relations.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdxcontent/200-orm/500-reference/325-prisma-config-reference.mdxcontent/200-orm/300-prisma-migrate/300-workflows/30-baselining.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/200-raw-queries.mdxcontent/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdxcontent/200-orm/050-overview/500-databases/880-supabase.mdxcontent/200-orm/500-reference/250-error-reference.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/100-typedsql.mdxcontent/200-orm/100-prisma-schema/20-data-model/50-database-mapping.mdxcontent/200-orm/300-prisma-migrate/300-workflows/80-unsupported-database-features.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdxcontent/200-orm/200-prisma-client/300-client-extensions/130-result.mdxcontent/200-orm/300-prisma-migrate/300-workflows/200-troubleshooting.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdxcontent/200-orm/050-overview/500-databases/600-mongodb.mdxcontent/200-orm/050-overview/600-beyond-prisma-orm.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/015-instantiate-prisma-client.mdxcontent/200-orm/200-prisma-client/100-queries/058-transactions.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/005-overview.mdxcontent/200-orm/050-overview/100-introduction/300-data-modeling.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdxcontent/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdxcontent/200-orm/050-overview/500-databases/840-cockroachdb.mdxcontent/200-orm/500-reference/050-prisma-client-reference.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdxcontent/200-orm/050-overview/500-databases/800-sql-server/index.mdxcontent/200-orm/050-overview/500-databases/890-neon.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-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: 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/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdxcontent/200-orm/200-prisma-client/300-client-extensions/110-client.mdxcontent/200-orm/200-prisma-client/300-client-extensions/index.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/100-connection-management.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdxcontent/200-orm/200-prisma-client/450-testing/100-unit-testing.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/index.mdxcontent/200-orm/200-prisma-client/300-client-extensions/100-model.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/300-working-with-composite-ids-and-constraints.mdxcontent/200-orm/200-prisma-client/300-client-extensions/120-query.mdxcontent/200-orm/200-prisma-client/100-queries/061-custom-validation.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdxcontent/200-orm/200-prisma-client/400-type-safety/index.mdxcontent/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdxcontent/200-orm/300-prisma-migrate/300-workflows/70-patching-and-hotfixing.mdxcontent/200-orm/300-prisma-migrate/300-workflows/90-development-and-production.mdxcontent/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdxcontent/200-orm/200-prisma-client/100-queries/070-case-sensitivity.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/050-overview/100-introduction/100-what-is-prisma.mdxcontent/200-orm/200-prisma-client/450-testing/150-integration-testing.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdxcontent/200-orm/200-prisma-client/100-queries/060-full-text-search.mdxcontent/200-orm/300-prisma-migrate/300-workflows/110-native-database-types.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/200-raw-queries.mdxcontent/200-orm/500-reference/250-error-reference.mdxcontent/200-orm/300-prisma-migrate/300-workflows/80-unsupported-database-features.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdxcontent/200-orm/200-prisma-client/300-client-extensions/130-result.mdxcontent/200-orm/300-prisma-migrate/300-workflows/200-troubleshooting.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdxcontent/200-orm/050-overview/500-databases/600-mongodb.mdxcontent/200-orm/050-overview/600-beyond-prisma-orm.mdxcontent/200-orm/200-prisma-client/100-queries/058-transactions.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/005-overview.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdxcontent/200-orm/050-overview/500-databases/300-postgresql.mdxcontent/200-orm/050-overview/500-databases/840-cockroachdb.mdxcontent/200-orm/500-reference/200-prisma-cli-reference.mdxcontent/200-orm/050-overview/500-databases/800-sql-server/index.mdxcontent/200-orm/050-overview/500-databases/890-neon.mdxcontent/200-orm/050-overview/500-databases/400-mysql.mdx
📚 Learning: 2025-10-03T19:30:57.554Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7157
File: content/800-guides/400-deno-integration.mdx:188-190
Timestamp: 2025-10-03T19:30:57.554Z
Learning: For the prisma/docs repository, do not suggest changes to code blocks when reviewing documentation pull requests.
Applied to files:
content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdxcontent/200-orm/200-prisma-client/450-testing/100-unit-testing.mdxcontent/200-orm/300-prisma-migrate/300-workflows/90-development-and-production.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.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/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdxcontent/200-orm/100-prisma-schema/20-data-model/65-externally-managed-tables.mdxcontent/200-orm/200-prisma-client/100-queries/061-custom-validation.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdxcontent/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdxcontent/200-orm/800-more/100-under-the-hood/100-engines.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdxcontent/200-orm/050-overview/500-databases/900-turso.mdxcontent/200-orm/100-prisma-schema/20-data-model/40-views.mdxcontent/200-orm/300-prisma-migrate/300-workflows/90-development-and-production.mdxcontent/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdxcontent/200-orm/200-prisma-client/100-queries/062-computed-fields.mdxcontent/200-orm/200-prisma-client/100-queries/064-custom-models.mdxcontent/200-orm/050-overview/500-databases/500-sqlite.mdxcontent/200-orm/100-prisma-schema/20-data-model/30-indexes.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/500-reference/300-environment-variables-reference.mdxcontent/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/03-fullstack.mdxcontent/200-orm/100-prisma-schema/20-data-model/10-models.mdxcontent/200-orm/050-overview/100-introduction/100-what-is-prisma.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdxcontent/200-orm/200-prisma-client/100-queries/060-full-text-search.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/01-rest.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdxcontent/200-orm/500-reference/325-prisma-config-reference.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/200-orm/200-prisma-client/100-queries/037-relation-queries.mdxcontent/200-orm/050-overview/500-databases/880-supabase.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/100-typedsql.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/005-overview.mdxcontent/200-orm/050-overview/100-introduction/300-data-modeling.mdxcontent/200-orm/100-prisma-schema/10-overview/index.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdxcontent/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdxcontent/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/200-read-replicas.mdxcontent/200-orm/050-overview/500-databases/300-postgresql.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdxcontent/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdxcontent/200-orm/050-overview/500-databases/840-cockroachdb.mdxcontent/200-orm/500-reference/200-prisma-cli-reference.mdxcontent/200-orm/200-prisma-client/100-queries/030-crud.mdxcontent/200-orm/500-reference/050-prisma-client-reference.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdxcontent/200-orm/050-overview/500-databases/800-sql-server/index.mdxcontent/200-orm/050-overview/500-databases/890-neon.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/485-deploy-to-vercel.mdxcontent/200-orm/050-overview/500-databases/400-mysql.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/200-orm/300-prisma-migrate/300-workflows/60-generating-down-migrations.mdxcontent/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdxcontent/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdxcontent/200-orm/800-more/100-under-the-hood/100-engines.mdxcontent/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdxcontent/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdxcontent/200-orm/100-prisma-schema/20-data-model/40-views.mdxcontent/200-orm/200-prisma-client/100-queries/062-computed-fields.mdxcontent/200-orm/100-prisma-schema/20-data-model/30-indexes.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/300-no-rust-engine.mdxcontent/200-orm/500-reference/300-environment-variables-reference.mdxcontent/200-orm/050-overview/500-databases/850-planetscale.mdxcontent/200-orm/200-prisma-client/100-queries/060-full-text-search.mdxcontent/200-orm/050-overview/300-prisma-in-your-stack/01-rest.mdxcontent/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/200-orm/200-prisma-client/100-queries/037-relation-queries.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/200-raw-queries.mdxcontent/200-orm/500-reference/250-error-reference.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/100-typedsql.mdxcontent/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdxcontent/200-orm/200-prisma-client/150-using-raw-sql/300-safeql.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdxcontent/200-orm/050-overview/600-beyond-prisma-orm.mdxcontent/200-orm/050-overview/500-databases/200-database-drivers.mdxcontent/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/005-overview.mdxcontent/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdxcontent/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdxcontent/200-orm/500-reference/200-prisma-cli-reference.mdxcontent/200-orm/200-prisma-client/100-queries/030-crud.mdxcontent/200-orm/500-reference/050-prisma-client-reference.mdxcontent/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.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/200-orm/200-prisma-client/300-client-extensions/100-model.mdxcontent/200-orm/200-prisma-client/300-client-extensions/120-query.mdxcontent/200-orm/200-prisma-client/700-debugging-and-troubleshooting/140-debugging.mdxcontent/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdxcontent/200-orm/300-prisma-migrate/300-workflows/50-squashing-migrations.mdxcontent/200-orm/200-prisma-client/100-queries/070-case-sensitivity.mdxcontent/200-orm/200-prisma-client/450-testing/150-integration-testing.mdxcontent/200-orm/050-overview/500-databases/880-supabase.mdxcontent/200-orm/500-reference/250-error-reference.mdxcontent/200-orm/300-prisma-migrate/300-workflows/80-unsupported-database-features.mdxcontent/200-orm/300-prisma-migrate/300-workflows/200-troubleshooting.mdx
📚 Learning: 2025-10-15T06:36:42.423Z
Learnt from: jy-joung-bitor
Repo: prisma/docs PR: 0
File: :0-0
Timestamp: 2025-10-15T06:36:42.423Z
Learning: The `tsc --init` command requires the `--types node` flag to properly include Node.js type definitions from `types/node` in the generated tsconfig.json, even when types/node is already installed. Without this flag, TypeScript may not automatically pick up Node.js typings.
Applied to files:
content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
🪛 LanguageTool
content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdx
[style] ~63-~63: Consider a more concise word here.
Context: ...org/en/blog/announcements/nodejs16-eol) in order to coincide with the end-of-life of OpenSS...
(IN_ORDER_TO_PREMIUM)
content/200-orm/200-prisma-client/100-queries/061-custom-validation.mdx
[grammar] ~24-~24: Use a hyphen to join words.
Context: ...ple, validations are only run on the top level data object passed to methods such...
(QB_NEW_EN_HYPHEN)
content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx
[grammar] ~16-~16: Use a hyphen to join words.
Context: ... changes to index configuration and full text indexes might be **breaking changes...
(QB_NEW_EN_HYPHEN)
[grammar] ~484-~484: Use a hyphen to join words.
Context: ...rning For now we do not enable the full text search commands in Prisma Client fo...
(QB_NEW_EN_HYPHEN)
content/200-orm/500-reference/300-environment-variables-reference.mdx
[style] ~84-~84: To form a complete sentence, be sure to include a subject.
Context: ....2.0 ::: PRISMA_GENERATE_NO_ENGINE` can be set to a truthy value to generate a ...
(MISSING_IT_THERE)
[style] ~84-~84: Consider a more concise word here.
Context: ...gine](/orm/more/under-the-hood/engines) in order to reduce deployed application size when p...
(IN_ORDER_TO_PREMIUM)
content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx
[style] ~20-~20: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...review-feature) referentialActions. - If you use version 2.25.0 or earlier, you ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~56-~56: As an alternative to the over-used intensifier ‘extremely’, consider replacing this phrase.
Context: ...om a version earlier than 2.26.0: It is extremely important that you check the [upgrade paths for r...
(EN_WEAK_ADJECTIVE)
content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx
[style] ~897-~897: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...ering using any of the null enums you can not use a shorthand and leave the equals ...
(CAN_NOT_PREMIUM)
content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx
[style] ~165-~165: Consider shortening or rephrasing this to strengthen your wording.
Context: ...Evolving your application Whenever you make changes to your database that are reflected in the...
(MAKE_CHANGES)
content/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdx
[grammar] ~327-~327: Ensure spelling is correct
Context: ...with a composite type that has a unique restraint, note that MongoDB does not enforce uni...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~467-~467: Ensure spelling is correct
Context: ...with a composite type that has a unique restraint, note that MongoDB does not enforce uni...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~634-~634: Ensure spelling is correct
Context: ...s in a composite type that has a unique restraint, note that MongoDB does not enforce uni...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
content/200-orm/200-prisma-client/100-queries/058-transactions.mdx
[style] ~1177-~1177: As a shorter alternative for ‘able to’, consider using “can”.
Context: ...nique field. - Since version 5.0.0 you are able to [filter on non-unique fields in `update...
(BE_ABLE_TO)
content/200-orm/200-prisma-client/100-queries/030-crud.mdx
[grammar] ~265-~265: Ensure spelling is correct
Context: ...sis not supported when using MongoDB, SQLServer, or SQLite. ::: createMany()` uses a...
(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). (2)
- GitHub Check: Check internal links
- GitHub Check: Cloudflare Pages
content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx
Show resolved
Hide resolved
content/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdx
Outdated
Show resolved
Hide resolved
Contributor
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 200-orm/200-prisma-client/100-queries/055-pagination.mdx
Errors in 200-orm/800-more/600-help-and-troubleshooting/050-dataguide/02-introduction-to-data-types.mdx
|
Contributor
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx (1)
157-179: Update prose or snippet to resolve the @prisma/client import mismatch (persistent issue from past review).The section "The
@prisma/clientnpm package" describes how the npm package mechanism works by default—where@prisma/clientre-exports.prisma/client. Line 170 states "you still import@prisma/client," but the snippet at line 173 imports from a custom output path instead.This mismatch was flagged in a previous review and remains unresolved. Since the entire document now uses custom output paths, update the prose to clarify that when using a custom output directory, you import from that generated path rather than from the npm package directly.
Suggested fix:
- This means that you still import `@prisma/client` in your own `.ts` files: + When using a custom output directory, you import `PrismaClient` from that generated path:Alternatively, if this section should document the default behavior, revert the snippet to import from
@prisma/clientand add a separate example showing the custom output import.
🧹 Nitpick comments (1)
content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx (1)
60-60: Optional: Refine wording for stronger documentation prose.The phrase "Feel free to customize" is casual but could be slightly more direct. Consider: "You can customize the output location to match your application structure."
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx(5 hunks)content/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdx(4 hunks)
🧰 Additional context used
🧠 Learnings (5)
📓 Common learnings
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.
Learnt from: 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: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: 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.
📚 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/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.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/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.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/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.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/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx
🪛 LanguageTool
content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx
[style] ~60-~60: Consider using a less common alternative to make your writing sound more unique and professional.
Context: .../generated" } ``` :::note Feel free to customize the output location to match ...
(FEEL_FREE_TO_STYLE_ME)
⏰ 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). (2)
- GitHub Check: Check internal links
- GitHub Check: Cloudflare Pages
🔇 Additional comments (6)
content/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdx (2)
10-14: MDX directive syntax conversions look good.The admonition markup has been properly converted from HTML to MDX directive syntax (:::warning and :::info). Content is preserved, and the closing
:::delimiters are correctly placed. The prior terminology fix ("unique constraint" vs "unique restraint") is present throughout.Also applies to: 325-329, 465-469, 632-636
33-41: Verify schema example scope in this PR.The AI summary indicates that generator provider examples should be updated from
"prisma-client-js"to"prisma-client"and datasource URLs should be removed. However, this file's schema example (lines 35 and 38–41) still shows the old pattern and isn't marked as changed. Please clarify whether the schema in this file was intentionally left unchanged, or if it should be updated to align with the broader PR objectives.content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx (4)
15-38: Generator config update is clear and well‑documented.The Rust-less setup example properly shows the new provider and output configuration, and the explanation of driver adapters is helpful context.
49-56: Generator config and setup workflow are well‑structured.The updated generator block with the new
prisma-clientprovider and explicitoutputpath is consistent with the PR changes and clearly guides users to define a custom output location.
98-126: Custom output path guidance is clear and consistent.The example progression and relative path imports align well with the PR's focus on custom output directories. The ESM compatibility note adds helpful context.
128-155: Verify prisma.config.ts and env() helper are documented and available.This section introduces a
prisma.config.tsconfiguration pattern with anenv()helper fromprisma/config. This is new in the documentation—please verify that this API exists in the current Prisma version being documented and is the recommended approach for environment variable loading in this context.[web]
Does Prisma ORM support prisma.config.ts with env() helper from prisma/config?
[/web]
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.
Summary by CodeRabbit
Documentation Updates
Configuration Changes
Adapter Updates
Formatting