fix: add callout to resolve studio error

[ankur-arch]

Summary by CodeRabbit

• Documentation
  • Added troubleshooting guidance for PostgreSQL schema parameter errors in Prisma Studio with resolution examples
  • Added troubleshooting steps for query engine caching issues affecting script execution

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR adds troubleshooting guidance to the Prisma Studio documentation, addressing PostgreSQL schema parameter configuration errors and query engine caching issues that can cause script execution failures. The additions include example URLs and remediation steps.

Changes

Cohort / File(s)	Summary
Prisma Studio troubleshooting documentation content/200-orm/400-tools/06-prisma-studio.mdx	Added PostgreSQL error troubleshooting for "unrecognized configuration parameter 'schema'" explaining that Studio forwards raw URLs to PostgreSQL and recommending the search_path option instead (appears twice in document). Added Terminal error troubleshooting for "Failed to run script" advising cache deletion to resolve query engine version conflicts.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Accuracy verification: Confirm the technical accuracy of troubleshooting steps, particularly the PostgreSQL search_path configuration and cache remediation paths. Verify the example URLs are correctly formatted and represent realistic problematic scenarios.
• Duplication rationale: The schema parameter troubleshooting appears twice—verify whether this intentional redundancy serves a pedagogical purpose or represents an oversight requiring consolidation.
• Completeness: Ensure cache folder paths cover all supported platforms and Prisma versions mentioned in the docs.

Possibly related PRs

• feat: add mentions of new Prisma Studio #7270: Overlaps on Prisma Studio troubleshooting content addressing cache/query engine issues in Terminal execution scenarios.
• fix: clarify studio better #7282: Modifies the same Prisma Studio documentation with guidance on direct database URL handling and introspection behavior directly relevant to the schema parameter troubleshooting added here.

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: adding troubleshooting callouts to Prisma Studio documentation to resolve specific errors (PostgreSQL schema parameter and caching issues).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2cf9b86 and 5503b14.

📒 Files selected for processing (1)

• content/200-orm/400-tools/06-prisma-studio.mdx (1 hunks)

🧰 Additional context used

🧠 Learnings (7)

📓 Common learnings

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7301
File: content/800-guides/410-cloudflare-workers.mdx:87-107
Timestamp: 2025-11-20T21:00:02.587Z
Learning: Do not suggest changes to `prisma.config.ts` files in the prisma/docs repository, as the code examples are intentional for documentation purposes.

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-11-20T21:00:02.587Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7301
File: content/800-guides/410-cloudflare-workers.mdx:87-107
Timestamp: 2025-11-20T21:00:02.587Z
Learning: Do not suggest changes to `prisma.config.ts` files in the prisma/docs repository, as the code examples are intentional for documentation purposes.

Applied to files:

• content/200-orm/400-tools/06-prisma-studio.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/200-orm/400-tools/06-prisma-studio.mdx

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

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".

Applied to files:

• content/200-orm/400-tools/06-prisma-studio.mdx

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

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

Applied to files:

• content/200-orm/400-tools/06-prisma-studio.mdx

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

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

Applied to files:

• content/200-orm/400-tools/06-prisma-studio.mdx

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

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

Applied to files:

• content/200-orm/400-tools/06-prisma-studio.mdx

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

• GitHub Check: Check internal links
• GitHub Check: Cloudflare Pages

🔇 Additional comments (2)

content/200-orm/400-tools/06-prisma-studio.mdx (2)

175-199: Well-written PostgreSQL troubleshooting guidance.

This new section clearly explains why the schema parameter fails (PostgreSQL doesn't recognize it), why it worked before (Prisma ORM v6 custom parameter), and provides accurate remediation using the standard search_path parameter with proper URL encoding. The examples are concrete and helpful, and the link to the GitHub issue provides additional context for users encountering this problem.

---

209-211: Practical caching troubleshooting guidance.

The cache deletion remedy is clear and helpful, with platform-specific paths for macOS/Linux and Windows. This directly addresses the error scenario and provides actionable next steps for users.

Tip

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

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

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

Example instruction:

"Divide the high-level summary into five sections:

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

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

---

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

[github-actions]

Dangerous URL check

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

[github-actions]

original	preview
content/200-orm/400-tools/06-prisma-studio.mdx	content/200-orm/400-tools/06-prisma-studio.mdx

[github-actions]

Redirect check

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

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

[github-actions]

🍈 Lychee Link Check Report

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

📊 Results Overview

Status	Count
🔍 Total	2242
✅ Successful	2208
⏳ Timeouts	0
🔀 Redirected	6
👻 Excluded	24
❓ Unknown	0
🚫 Errors	3
⛔ Unsupported	1

Errors per input

Errors in 200-orm/200-prisma-client/150-using-raw-sql/200-raw-queries.mdx

• [404] https://www.mongodb.com/docs/manual/reference/operator/aggregation-pipeline | Error (cached)
• [404] https://www.mongodb.com/docs/manual/reference/operator/query | Error (cached)

Errors in 200-orm/800-more/400-comparisons/03-prisma-and-mongoose.mdx

• [404] https://www.mongodb.com/docs/manual/reference/operator/query/#query-selectors | Error (cached)

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	5503b14
Status:	✅  Deploy successful!
Preview URL:	https://6c68d97a.docs-51g.pages.dev
Branch Preview URL:	https://dc-6338-callout-studio-docs.docs-51g.pages.dev

View logs