-
Notifications
You must be signed in to change notification settings - Fork 854
feat: restructure getting started side nav #7244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* `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
|
Caution Review failedThe pull request is closed. WalkthroughLarge docs reorganization: many legacy per-database "start-from-scratch" and example pages were removed and consolidated into a new Prisma ORM section with database-specific quickstarts and shared MDX components; sidebar, redirects, middleware docs, Prisma config/generator docs, CI (Lychee) and repo config were also updated (docs/content and tooling changes only). Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Focus review on:
Possibly related PRs
Pre-merge checks✅ Passed checks (3 passed)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
content/250-postgres/400-query-optimization/100-setup.mdx (1)
70-76: Fix incorrect import forwithAccelerateextension.The
withAcceleratefunction is imported from the wrong package. According to the Accelerate getting-started guide (filecontent/300-accelerate/200-getting-started.mdxline 135), it should be imported from@prisma/extension-accelerate, not@prisma/extension-optimize. This import error will cause a runtime failure.import { PrismaClient } from "@prisma/client"; -import { withAccelerate } from "@prisma/extension-optimize"; +import { withAccelerate } from "@prisma/extension-accelerate"; import { withOptimize } from "@prisma/extension-optimize"; const prisma = new PrismaClient().$extends( withOptimize({ apiKey: process.env.OPTIMIZE_API_KEY }), ).$extends(withAccelerate());content/200-orm/500-reference/325-prisma-config-reference.mdx (1)
510-523: Fix minor typo.
“here’s how how need to place the migrations folder:” → “here’s how you need to place the migrations folder:”.-For example, assuming `schema.prisma` defines the `datasource`, here's how how need to place the migrations folder: +For example, assuming `schema.prisma` defines the `datasource`, here's how you need to place the migrations folder:
🧹 Nitpick comments (13)
content/800-guides/140-use-prisma-in-pnpm-workspaces.mdx (1)
357-357: Use sentence case for the "Next steps" heading.Per the docs style guide, all headings should use sentence case, not title case. "Next Steps" should be "Next steps".
Based on learnings
-## Next Steps +## Next stepscontent/700-optimize/200-getting-started.mdx (1)
2-2: Use sentence case for page title.The
titlefield should use sentence case ("Getting started") rather than title case ("Getting Started"), consistent with the learning guidelines for Prisma docs and the formatting used in the Accelerate getting-started file.- title: 'Getting Started' + title: 'Getting started'content/200-orm/200-prisma-client/300-client-extensions/120-query.mdx (1)
18-18: Reduce repeated sentence openings for better flow.The sentence "You can use..." followed by "You can bind..." uses the same opening structure twice in quick succession, which can feel repetitive. Consider restructuring to vary the cadence—for example, combining ideas or using an action verb: "Create independent clients with customized behavior by using the
querycomponent to bind specific filters or users to individual client instances."content/100-getting-started/_components/_install-prisma-client.mdx (1)
77-83: Tighten note block to reduce repeated phrasing.The note mentions "Prisma schema" twice in back-to-back sentences (lines 79-81). Consider combining or rephrasing to strengthen the explanation. For example: "When you run
prisma generate, you're creating code tailored to your Prisma schema. Whenever your schema changes—either manually or throughprisma migrate devorprisma db push—you need to re-runprisma generate(which those commands do automatically)."This is a minor readability improvement; the current version is functional.
content/200-orm/500-reference/100-prisma-schema-reference.mdx (2)
21-23: v7 deprecations: request confirmation + cross-link.
Please confirm these fields are deprecated in Prisma ORM v7 GA and that Prisma Config fully replaces them across all connectors. If confirmed, consider adding a one‑line “Migration tip” pointing to an upgrade guide from schema URLs to Prisma Config.Also applies to: 27-29
168-169: Clarify status ofprisma-client-js.
You note it's the default for 6.x. If it’s also deprecated in v7, add a parenthetical “deprecated in v7” and link to the recommendedprisma-clientgenerator section for quick migration.content/200-orm/500-reference/325-prisma-config-reference.mdx (1)
612-639: Env loading: set expectation about whendotenvis required.
Consider adding one sentence: “If your runtime or tooling already loads.env(e.g., Bun), you don’t needdotenv.” You mention Bun later, but calling it out up front reduces confusion.content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx (3)
36-39: Adapter package: MySQL vs MariaDB.
This guide targets MySQL but installs@prisma/adapter-mariadb. If MySQL is the primary target, consider using the MySQL adapter. If MariaDB is intentionally recommended for both, call this out explicitly here.
131-142: Consistency with Prisma Config deprecation.
Schema omitsurl(good if moving URLs to Prisma Config). Ensure all quickstarts follow the same pattern to avoid user confusion.
212-227: Confirm constructor options forPrismaMariaDb.
Verify the expected option names and types (host,user,password,database,connectionLimit). If the adapter accepts a URL instead, prefer passingprocess.env.DATABASE_URLfor parity with config.content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx (1)
124-136: Align schema URL placement across quickstarts.
This guide includesurl = env("DATABASE_URL")in the schema while the MySQL guide moves URLs to Prisma Config. Pick one approach (prefer Prisma Config if v7 docs) and apply consistently, or add a short note explaining both are supported.content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx (1)
102-117: Engine setting: call out rationale.
You setengine: "classic"here. If that’s required for MongoDB in v7 (or optional), add a short note so users know when to useclassicvsjs.content/200-orm/100-prisma-schema/10-overview/03-generators.mdx (1)
18-18: Clarify the wording of the default generator statement.Line 18 currently reads: "The default generator for Prisma Client is
prisma-client, which outputs plain TypeScript code and requires a customoutputpath". Consider emphasizing that this is the new default as of v7 (per line 38) to avoid confusion for users familiar with earlier versions. The statement is accurate but could be slightly clearer about the version context.Consider rephrasing to:
- The default generator for Prisma Client is `prisma-client`, which outputs plain TypeScript code and _requires_ a custom `output` path (read more about it [here](https://www.prisma.io/blog/why-prisma-orm-generates-code-into-node-modules-and-why-it-ll-change)). + As of Prisma ORM v7, the default generator is `prisma-client`, which outputs plain TypeScript code and _requires_ a custom `output` path (read more about it [here](https://www.prisma.io/blog/why-prisma-orm-generates-code-into-node-modules-and-why-it-ll-change)).
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (69)
.coderabbit.yaml(2 hunks).github/workflows/lychee.yml(2 hunks)content/100-getting-started/01-quickstart-prismaPostgres.mdx(1 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/03-prisma-postgres/100-from-the-cli.mdx(8 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx(1 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdx(1 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/300-typeorm.mdx(1 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdx(1 hunks)content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx(6 hunks)content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx(5 hunks)content/100-getting-started/03-prisma-postgres/120-upgrade-from-early-access.mdx(0 hunks)content/100-getting-started/_components/_create-prisma-client.mdx(1 hunks)content/100-getting-started/_components/_create-project.mdx(1 hunks)content/100-getting-started/_components/_explore-data.mdx(1 hunks)content/100-getting-started/_components/_install-prisma-client.mdx(1 hunks)content/100-getting-started/_components/_next-steps.mdx(1 hunks)content/100-getting-started/_components/_prerequisites.mdx(1 hunks)content/100-getting-started/_components/_prisma-init.mdx(1 hunks)content/200-orm/025-getting-started/10-quickstart.mdx(1 hunks)content/200-orm/025-getting-started/20-add-to-existing-project.mdx(1 hunks)content/200-orm/025-getting-started/_category_.json(1 hunks)content/200-orm/025-getting-started/index.mdx(1 hunks)content/200-orm/100-prisma-schema/10-overview/02-data-sources.mdx(1 hunks)content/200-orm/100-prisma-schema/10-overview/03-generators.mdx(3 hunks)content/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdx(1 hunks)content/200-orm/200-prisma-client/100-queries/100-query-optimization-performance.mdx(0 hunks)content/200-orm/200-prisma-client/300-client-extensions/120-query.mdx(1 hunks)content/200-orm/200-prisma-client/300-client-extensions/500-middleware/100-soft-delete-middleware.mdx(0 hunks)content/200-orm/200-prisma-client/300-client-extensions/500-middleware/200-logging-middleware.mdx(0 hunks)content/200-orm/200-prisma-client/300-client-extensions/500-middleware/300-session-data-middleware.mdx(0 hunks)content/200-orm/200-prisma-client/300-client-extensions/500-middleware/index.mdx(0 hunks)content/200-orm/200-prisma-client/300-client-extensions/index.mdx(0 hunks)content/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdx(1 hunks)content/200-orm/500-reference/050-prisma-client-reference.mdx(0 hunks)content/200-orm/500-reference/100-prisma-schema-reference.mdx(2 hunks)content/200-orm/500-reference/325-prisma-config-reference.mdx(2 hunks)content/200-orm/500-reference/400-system-requirements.mdx(2 hunks)content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx(1 hunks)content/200-orm/800-more/350-ai-tools/100-cursor.mdx(0 hunks)content/200-orm/800-more/350-ai-tools/300-windsurf.mdx(0 hunks)content/200-orm/800-more/350-ai-tools/400-github-copilot.mdx(0 hunks)content/250-postgres/300-database/650-direct-connections.mdx(1 hunks)content/250-postgres/400-query-optimization/100-setup.mdx(2 hunks)content/250-postgres/50-getting-started/100-quickstart.mdx(1 hunks)content/250-postgres/50-getting-started/200-import-from-existing-database.mdx(1 hunks)content/250-postgres/50-getting-started/_category_.json(1 hunks)content/250-postgres/50-getting-started/index.mdx(2 hunks)content/300-accelerate/200-getting-started.mdx(1 hunks)content/700-optimize/200-getting-started.mdx(1 hunks)content/800-guides/140-use-prisma-in-pnpm-workspaces.mdx(4 hunks)sidebars.ts(2 hunks)src/css/custom.css(1 hunks)static/_redirects(1 hunks)
💤 Files with no reviewable changes (11)
- content/200-orm/200-prisma-client/300-client-extensions/500-middleware/index.mdx
- content/200-orm/800-more/350-ai-tools/400-github-copilot.mdx
- content/200-orm/200-prisma-client/300-client-extensions/500-middleware/200-logging-middleware.mdx
- content/200-orm/200-prisma-client/300-client-extensions/index.mdx
- content/200-orm/800-more/350-ai-tools/100-cursor.mdx
- content/200-orm/200-prisma-client/300-client-extensions/500-middleware/100-soft-delete-middleware.mdx
- content/200-orm/800-more/350-ai-tools/300-windsurf.mdx
- content/200-orm/200-prisma-client/100-queries/100-query-optimization-performance.mdx
- content/200-orm/200-prisma-client/300-client-extensions/500-middleware/300-session-data-middleware.mdx
- content/100-getting-started/03-prisma-postgres/120-upgrade-from-early-access.mdx
- content/200-orm/500-reference/050-prisma-client-reference.mdx
🧰 Additional context used
🧠 Learnings (9)
📓 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-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/400-query-optimization/100-setup.mdxcontent/200-orm/100-prisma-schema/10-overview/03-generators.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/_components/_explore-data.mdxcontent/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdxcontent/200-orm/200-prisma-client/000-setup-and-configuration/010-generating-prisma-client.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/200-orm/500-reference/325-prisma-config-reference.mdxcontent/100-getting-started/_components/_prisma-init.mdxcontent/100-getting-started/_components/_install-prisma-client.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdxcontent/100-getting-started/_components/_create-prisma-client.mdxcontent/200-orm/100-prisma-schema/10-overview/02-data-sources.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/_components/_create-project.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/800-guides/140-use-prisma-in-pnpm-workspaces.mdxcontent/250-postgres/50-getting-started/index.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/100-getting-started/02-prisma-orm/100-quickstart/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/100-quickstart/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdxcontent/100-getting-started/01-quickstart-prismaPostgres.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/300-typeorm.mdxcontent/250-postgres/50-getting-started/200-import-from-existing-database.mdxcontent/100-getting-started/_components/_explore-data.mdxcontent/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdxstatic/_redirectscontent/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/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/200-orm/025-getting-started/20-add-to-existing-project.mdxcontent/200-orm/500-reference/325-prisma-config-reference.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/500-sql-server.mdxcontent/100-getting-started/_components/_prisma-init.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdxcontent/100-getting-started/_components/_install-prisma-client.mdxcontent/250-postgres/50-getting-started/100-quickstart.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/200-orm/025-getting-started/10-quickstart.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdxcontent/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdxcontent/100-getting-started/_components/_create-prisma-client.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdxcontent/200-orm/025-getting-started/index.mdxsidebars.tscontent/800-guides/140-use-prisma-in-pnpm-workspaces.mdxcontent/250-postgres/50-getting-started/index.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/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/100-quickstart/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/300-typeorm.mdxcontent/100-getting-started/_components/_explore-data.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdxcontent/200-orm/500-reference/100-prisma-schema-reference.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/200-orm/500-reference/325-prisma-config-reference.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdxcontent/100-getting-started/_components/_prisma-init.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdxcontent/100-getting-started/_components/_install-prisma-client.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/200-orm/025-getting-started/10-quickstart.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdxcontent/100-getting-started/_components/_prerequisites.mdxcontent/100-getting-started/_components/_create-prisma-client.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/_components/_create-project.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdxcontent/200-orm/025-getting-started/index.mdxsidebars.tscontent/800-guides/140-use-prisma-in-pnpm-workspaces.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/800-mongodb.mdxcontent/200-orm/200-prisma-client/300-client-extensions/120-query.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/300-typeorm.mdxcontent/250-postgres/50-getting-started/200-import-from-existing-database.mdxcontent/100-getting-started/_components/_explore-data.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/_components/_prisma-init.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdxcontent/100-getting-started/_components/_install-prisma-client.mdxcontent/250-postgres/50-getting-started/100-quickstart.mdxcontent/100-getting-started/_components/_next-steps.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/200-orm/025-getting-started/10-quickstart.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdxcontent/100-getting-started/_components/_prerequisites.mdxcontent/100-getting-started/_components/_create-prisma-client.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdxsidebars.tscontent/800-guides/140-use-prisma-in-pnpm-workspaces.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/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdxcontent/200-orm/025-getting-started/index.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/100-quickstart/700-cockroachdb.mdxcontent/200-orm/100-prisma-schema/10-overview/03-generators.mdxcontent/200-orm/500-reference/400-system-requirements.mdxcontent/200-orm/500-reference/500-preview-features/050-client-preview-features.mdxcontent/800-guides/140-use-prisma-in-pnpm-workspaces.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/100-getting-started/_components/_create-project.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/800-guides/140-use-prisma-in-pnpm-workspaces.mdx
🪛 LanguageTool
content/200-orm/200-prisma-client/300-client-extensions/120-query.mdx
[style] ~18-~18: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ndent clients with customized behavior. You can bind one client to a specific filte...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/400-mysql.mdx
[style] ~222-~222: 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] ~188-~188: 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] ~22-~22: Consider a more concise word here.
Context: ...from-mongoose). ::: ## Prerequisites In order to successfully complete this guide, you n...
(IN_ORDER_TO_PREMIUM)
[style] ~248-~248: Consider shortening or rephrasing this to strengthen your wording.
Context: ...ma MongoDB does not use 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/200-sqlite.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/100-prisma-postgres.mdx
[style] ~207-~207: 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/_components/_install-prisma-client.mdx
[style] ~79-~79: Consider shortening or rephrasing this to strengthen your wording.
Context: ...red to your Prisma schema. Whenever you make changes to your Prisma schema, you need to update ...
(MAKE_CHANGES)
content/100-getting-started/_components/_create-prisma-client.mdx
[style] ~172-~172: Using many exclamation marks might seem excessive (in this case: 8 exclamation marks for a text that’s 4939 characters long)
Context: ...rismaClient() if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma ...
(EN_EXCESSIVE_EXCLAMATION)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.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/03-prisma-postgres/100-from-the-cli.mdx
[locale-violation] ~394-~394: In American English, ‘afterward’ is the preferred variant. ‘Afterwards’ is more commonly used in British English and other dialects.
Context: ... Post record in a nested write query. Afterwards, you'll see how you can retrieve the re...
(AFTERWARDS_US)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.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)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: Check links
- GitHub Check: Check internal links
- GitHub Check: runner / linkspector
- GitHub Check: Cloudflare Pages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Nitpick comments (5)
content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx (1)
1-6: Metadata frontmatter looks good; consider metaTitle casing alignment.The frontmatter is well-structured. Per learnings, all user-facing headings correctly use sentence case. One observation: the
metaTitlecontains "Quickstart:" in title case. If metadata titles must also follow strict sentence-case rules (like content headings), consider:"Quickstart: Prisma ORM with Prisma Postgres (5 min)"→"Quickstart: Prisma ORM with Prisma Postgres (5 min)"— however, SEO metadata often uses title case conventions, so this may be intentional and outside the scope of the content heading guidelines.content/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdx (1)
142-160: Consider adding clarity to separate environment variable usage.The
.envsection shows individual variables (DB_USER, DB_PASSWORD, etc.) but the replacement guidance only explains the DATABASE_URL format. Since these individual variables are later used inlib/prisma.ts(line 216–219), users might appreciate a brief note clarifying that these values are extracted from the DATABASE_URL and should match the credentials you provide there.Example addition after line 159:
The separate environment variables (DB_USER, DB_PASSWORD, DB_NAME, HOST) are also needed because the Prisma adapter for SQL Server uses them to construct the connection separately from Prisma's configuration.content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx (1)
535-535: Consider stronger phrasing for the next steps section.The phrase "If you want to explore more complex queries" is conversational but could be slightly more direct. Consider: "To explore more complex queries, such as adding caching functionality, check out the official Quickstart" This is a minor style suggestion for the "chill" review mode.
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx (2)
21-41: Minor wording refinement for conciseness.Line 22 ("In order to successfully complete") can be shortened to "To successfully complete" for tighter prose. This is a stylistic preference and not required.
246-294: Minor wording refinement on schema evolution heading context.Line 248's "To make changes to your database schema" can be tightened to "To modify your database schema" or aligned with the section title "Evolve your schema" for consistency. Again, optional and stylistic.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (167)
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/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)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-cockroachdb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-mysql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-postgresql.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-sqlserver.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/300-next-steps.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/_install-prisma-client-partial.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-node-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-typescript-mongodb.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/300-next-steps.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/_prisma-init-partial.mdx(0 hunks)content/100-getting-started/02-setup-prisma/200-add-to-existing-project/index.mdx(0 hunks)content/100-getting-started/02-setup-prisma/index.mdx(0 hunks)content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx(8 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx(1 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdx(1 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdx(1 hunks)
💤 Files with no reviewable changes (154)
- 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/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-postgresql.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/index.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/110-relational-databases/170-baseline-your-database-typescript-sqlserver.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-node-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/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.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/100-connect-your-database-node-mysql.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/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-mysql.mdx
- content/100-getting-started/02-setup-prisma/index.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/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/100-connect-your-database-typescript-planetscale.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/100-connect-your-database-node-mongodb.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/120-mongodb-typescript-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/200-add-to-existing-project/index.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/100-start-from-scratch/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/110-relational-databases/275-evolve-your-schema-node-mysql.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/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/200-install-prisma-client-typescript-mysql.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-planetscale.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/100-start-from-scratch/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/250-querying-the-database-node-postgresql.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/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/170-baseline-your-database-node-cockroachdb.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/200-add-to-existing-project/120-mongodb/100-connect-your-database-typescript-mongodb.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/110-relational-databases/150-using-prisma-migrate-typescript-planetscale.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/120-mongodb/100-connect-your-database-typescript-mongodb.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/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-postgresql.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/120-mongodb/125-creating-the-prisma-schema-node-mongodb.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-typescript-mysql.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/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.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-mysql.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/170-baseline-your-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/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/150-introspection-typescript-postgresql.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/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/150-introspection-typescript-planetscale.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/_install-prisma-client-partial.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-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/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/150-using-prisma-migrate-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/100-start-from-scratch/120-mongodb/100-connect-your-database-node-mongodb.mdx
- 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/250-querying-the-database-node-planetscale.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/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-prismaPostgres.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/01-quickstart-sqlite.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/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-typescript-sqlserver.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/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-cockroachdb.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/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/250-querying-the-database-node-sqlserver.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/100-start-from-scratch/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-typescript-sqlserver.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/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-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/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/120-mongodb/250-querying-the-database-node-mongodb.mdx
- 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/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/275-evolve-your-schema-typescript-mysql.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/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-sqlserver.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/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-node-mysql.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/150-introspection-node-postgresql.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/200-add-to-existing-project/110-relational-databases-typescript-postgresql.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/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.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/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-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/01-quickstart-prismaPostgres.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-sqlserver.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-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/120-mongodb/125-introspection-typescript-mongodb.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/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/200-install-prisma-client-node-planetscale.mdx
- content/100-getting-started/02-setup-prisma/100-start-from-scratch/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/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-cockroachdb.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/200-add-to-existing-project/110-relational-databases/300-next-steps.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/250-querying-the-database-node-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/100-start-from-scratch/110-relational-databases-node-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/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-sqlserver.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/_prisma-init-partial.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/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/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/100-connect-your-database-typescript-postgresql.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/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/100-connect-your-database-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-typescript-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/170-baseline-your-database-typescript-cockroachdb.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-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/120-mongodb-typescript-mongodb.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/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/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-postgresql.mdx
✅ Files skipped from review due to trivial changes (1)
- content/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx
🚧 Files skipped from review as they are similar to previous changes (4)
- content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdx
🧰 Additional context used
🧠 Learnings (6)
📓 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".
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: 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/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.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/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.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/500-sql-server.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.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/500-sql-server.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.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/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx
🪛 LanguageTool
content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx
[locale-violation] ~394-~394: In American English, ‘afterward’ is the preferred variant. ‘Afterwards’ is more commonly used in British English and other dialects.
Context: ... Post record in a nested write query. Afterwards, you'll see how you can retrieve the re...
(AFTERWARDS_US)
[style] ~535-~535: Consider using an alternative to strengthen your wording.
Context: ...h a basic Prisma Postgres setup. If you want to explore more complex queries, such a...
(WANT_KEEN)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
[style] ~22-~22: Consider a more concise word here.
Context: ...from-mongoose). ::: ## Prerequisites In order to successfully complete this guide, you n...
(IN_ORDER_TO_PREMIUM)
[style] ~248-~248: Consider shortening or rephrasing this to strengthen your wording.
Context: ...ma MongoDB does not use migrations. To make changes to your database schema: ### 8.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). (4)
- GitHub Check: Check links
- GitHub Check: runner / linkspector
- GitHub Check: Check internal links
- GitHub Check: Cloudflare Pages
content/100-getting-started/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdx (1)
192-220: Strengthen the wording in the schema evolution section.The phrasing "To make changes to your database schema:" before Section 8.1 feels indirect. Consider consolidating or rephrasing to be more direct, such as "Update your database schema using PlanetScale's branching workflow:" or similar.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (9)
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/600-planetscale.mdx(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- content/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdx
🚧 Files skipped from review as they are similar to previous changes (5)
- content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx
🧰 Additional context used
🧠 Learnings (5)
📓 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".
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: 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/400-mysql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.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/400-mysql.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdxcontent/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.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/200-add-to-existing-project/600-planetscale.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/100-quickstart/600-planetscale.mdx
🪛 LanguageTool
content/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdx
[style] ~194-~194: 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)
⏰ 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: runner / linkspector
- GitHub Check: Check internal links
🔇 Additional comments (6)
content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx (2)
1-296: Overall: comprehensive and well-structured quickstart.The guide flows logically from prerequisites through first queries, with clear explanations at each step. All headings follow sentence case conventions, code examples are syntactically sound and appropriate for documentation, placeholder credentials are clearly marked for replacement, and the progression from schema definition to data exploration is instructive. With the .env comment syntax corrected, this is a solid quickstart resource.
147-156: Use#for .env file comments instead of//.The
.envfile syntax uses#for comments, not//. Updating lines 149 and 155 will ensure the code snippet is syntactically correct if copied directly.Apply this diff:
```env file=.env DATABASE_URL="mysql://username:password@localhost:3306/mydb" -//add-start +# add-start DATABASE_USER="username" DATABASE_PASSWORD="password" DATABASE_NAME="mydb" DATABASE_HOST="localhost" DATABASE_PORT=3306 -//add-end +# add-end<details> <summary>⛔ Skipped due to learnings</summary>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.mdxfiles, 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: 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 filecontent/200-orm/800-more/600-help-and-troubleshooting/050-dataguide/050-database-glossary.mdxin future reviews as per user request. Issues in this file were addressed in PR #7185.</details> </blockquote></details> <details> <summary>content/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdx (3)</summary><blockquote> `52-77`: **Well-structured ESM configuration for new projects.** The explicit ESM setup section (tsconfig.json and package.json) is a valuable addition that correctly distinguishes this quickstart from the "add to existing" variant. This helps developers avoid runtime errors when using ESM with Prisma. --- `244-285`: **Clear and runnable first query example.** The example nicely demonstrates both create and read operations, providing learners with tangible success criteria. The error handling and disconnection pattern is solid for a starter guide. --- `1-7`: **Standardize frontmatter key between PlanetScale quickstart and "add to existing" guides.** File 1 uses `sidebar_label: 'PlanetScale'` while the companion guide (`content/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdx`) uses `sidebar_title: 'PlanetScale'`. Choose one key consistently across both files to ensure predictable sidebar rendering and avoid potential navigation conflicts. <details> <summary>⛔ Skipped due to learnings</summary>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.mdxfiles, 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: 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: 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 filecontent/200-orm/800-more/600-help-and-troubleshooting/050-dataguide/050-database-glossary.mdxin future reviews as per user request. Issues in this file were addressed in PR #7185.</details> </blockquote></details> <details> <summary>content/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdx (1)</summary><blockquote> `1-7`: **This review comment should be dismissed—the frontmatter keys are intentionally different by design.** The pattern across the entire codebase is crystal clear: "quickstart" guides consistently use `sidebar_label`, while "add-to-existing-project" guides consistently use `sidebar_title`. This isn't a bug; it's an intentional distinction between the two guide types. The file under review correctly follows the established convention for its category. > Likely an incorrect or invalid review comment. </blockquote></details> </blockquote></details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (2)
content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx (1)
398-398: Prefer American English "afterward".Per American English conventions, use "afterward" instead of "afterwards" in this sentence.
-One of the main features of Prisma ORM is the ease of working with [relations](/orm/prisma-schema/data-model/relations). Afterwards, you'll see how you can retrieve the relation from the database using the `include` option. +One of the main features of Prisma ORM is the ease of working with [relations](/orm/prisma-schema/data-model/relations). Afterward, you'll see how you can retrieve the relation from the database using the `include` option.content/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdx (1)
209-214: Optional: Strengthen the transition at section 9.The phrasing "To make changes to your database schema:" is slightly passive for a section introduction. Consider: "To evolve your database schema, follow these steps:" or simply move directly to the subsection. This is a minor polish point.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (11)
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/200-sqlite.mdx(1 hunks)content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx(8 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdx(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (8)
- content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdx
- content/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.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".
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: 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/200-add-to-existing-project/200-sqlite.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.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/200-add-to-existing-project/200-sqlite.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/200-add-to-existing-project/200-sqlite.mdxcontent/100-getting-started/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.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/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.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/03-prisma-postgres/100-from-the-cli.mdxcontent/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.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/100-quickstart/600-planetscale.mdx
🪛 LanguageTool
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/03-prisma-postgres/100-from-the-cli.mdx
[locale-violation] ~398-~398: In American English, ‘afterward’ is the preferred variant. ‘Afterwards’ is more commonly used in British English and other dialects.
Context: ... Post record in a nested write query. Afterwards, you'll see how you can retrieve the re...
(AFTERWARDS_US)
[style] ~539-~539: Consider using an alternative to strengthen your wording.
Context: ...h a basic Prisma Postgres setup. If you want to explore more complex queries, such a...
(WANT_KEEN)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: Check links
- GitHub Check: Check internal links
- GitHub Check: runner / linkspector
- GitHub Check: Cloudflare Pages
🔇 Additional comments (5)
content/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdx (1)
1-311: Comprehensive and well-structured quickstart guide.This new PlanetScale quickstart is excellent work. The guide flows logically from setup through to running queries, with clear step-by-step instructions. Sentence case is applied consistently throughout all headings, product names are preserved correctly (Prisma ORM, PlanetScale), and PlanetScale-specific considerations are properly highlighted—particularly the
relationMode = "prisma"requirement and the mandatory index on foreign keys (line 208).The code examples are practical and complete, from ESM configuration through to a realistic script that demonstrates both create and findMany operations with proper error handling and disconnection. The use of shared MDX components for prerequisites, project creation, and next steps maintains consistency across the quickstart suite.
content/100-getting-started/03-prisma-postgres/100-from-the-cli.mdx (3)
116-194: Well-structured ESM and prisma.config.ts setup.The new ESM configuration (lines 116–141) and the centralized
prisma.config.tspattern (lines 159–194) are clearly presented with step-by-step guidance. The introduction ofdotenv/configensures environment variables are properly loaded. The syntax and explanations are accurate, and the approach aligns with modern Node.js practices for ES modules.
251-266: Centralized Prisma Client instantiation is well-documented.The new
lib/prisma.tsmodule (lines 251–266) properly demonstrates the singleton pattern for PrismaClient with the@prisma/adapter-pgadapter and environment variable handling. All subsequent code examples correctly import from this centralized instance, ensuring consistency throughout the guide.
143-157: Package dependency explanations enhance clarity.The added explanations for each package (lines 152–157)—including
@prisma/adapter-pgfor the node-postgres driver anddotenvfor environment loading—help developers understand why each dependency is necessary. This is particularly valuable for developers new to Prisma Postgres.content/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdx (1)
1-260: Well-structured new guide with proper documentation conventions.This new SQLite add-to-existing-project guide follows the established patterns in the PR:
- ✓ All headings use sentence case (exception: product names preserved correctly)
- ✓ Reusable MDX components imported and placed appropriately (Prerequisites, ExploreData, NextSteps)
- ✓ Code blocks are syntactically correct with no exposed secrets
- ✓ Step-by-step flow is logical and easy to follow
- ✓ Proper front matter with badge, meta descriptions
The guide successfully parallels the structure of other database quickstarts while providing SQLite-specific setup instructions, including custom Prisma config paths and the better-sqlite3 adapter integration.
Dangerous URL checkNo absolute URLs to prisma.io/docs found. |
Redirect checkThis PR probably requires the following redirects to be added to static/_redirects: |
🍈 Lychee Link Check Report
📊 Results Overview
|
🍈 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/300-upgrade-guides/800-upgrade-from-prisma-1/06-upgrading-prisma-binding-to-sdl-first.mdx
|
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdx
Errors in 800-guides/400-deno-integration.mdx
|
Summary by CodeRabbit
New Features
Deprecations
Documentation