docs: add ppg connection pooling ga changes#7594
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
WalkthroughUpdated Prisma Postgres documentation to introduce and recommend pooled TCP connection strings for serverless and high-concurrency workloads, replace query-parameter pooling examples with dedicated pooled TCP URLs, add a step-by-step enabling workflow, and clarify differences between direct and pooled TCP connections across three docs. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/docs/content/docs/postgres/database/connection-pooling.mdx`:
- Around line 17-23: Update the pooled connection example by fixing the domain
in the pooled DATABASE_URL entry: change the host from db.prisma.ie to
db.prisma.io so the pooled connection string (the second DATABASE_URL example)
matches the correct Prisma domain used for pooled TCP connections.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: bbd1c741-4859-4c68-a3e7-17f03ae86954
📒 Files selected for processing (3)
apps/docs/content/docs/orm/reference/connection-urls.mdxapps/docs/content/docs/postgres/database/connection-pooling.mdxapps/docs/content/docs/postgres/database/direct-connections.mdx
b83dc22
Summary by CodeRabbit