AMS

[asmaems411-411]

Summary by CodeRabbit

• Documentation
  • Updated the Prisma schema examples for PostgreSQL and MongoDB.
  • Replaced the MongoDB sample data model with expanded user, subscription, authentication, lead, messaging, appointment, and knowledge entities.
  • Revised relationships, defaults, identifiers, timestamps, and field types throughout the examples.

[vercel]

@asmaems411-411 is attempting to deploy a commit to the Prisma Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

Changes

Prisma schema documentation

Layer / File(s)	Summary
PostgreSQL datasource example apps/docs/content/docs/orm/prisma-schema/overview/index.mdx	Updates the datasource block to use the PostgreSQL provider.
MongoDB schema model example apps/docs/content/docs/orm/prisma-schema/overview/index.mdx	Replaces the previous User, Post, and Role definitions with expanded User, Lead, Message, Appointment, and Knowledge models and their relations.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is too vague to convey the Prisma schema documentation changes in this pull request.	Use a short, specific title that names the main change, such as the Prisma schema doc update or the new MongoDB example models.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

Warning

⚠️ This pull request has been flagged as potential spam (vandalism) by CodeRabbit slop detection and should be reviewed carefully.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/docs/content/docs/orm/prisma-schema/overview/index.mdx`:
- Line 17: Update the createdAt field in the Prisma schema example to use the
valid case-sensitive DateTime scalar instead of datetime, matching the existing
type usage in the surrounding model.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a0de600e-d20e-46b1-b503-d15268095769

📥 Commits

Reviewing files that changed from the base of the PR and between fb5c8ca and 3f196b5.

📒 Files selected for processing (1)

• apps/docs/content/docs/orm/prisma-schema/overview/index.mdx

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Fix invalid Prisma type: datetime should be DateTime.

Line 17 uses datetime (lowercase), which is not a valid Prisma scalar type. Prisma type names are case-sensitive — the correct type is DateTime, as correctly used on line 18 and in every other model in this schema. A user copying this example would hit a schema validation error.

🔧 Proposed fix

-  createdAt        datetime      `@default`(now())
+  createdAt        DateTime      `@default`(now())

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	createdAt datetime @default(now())
	createdAt DateTime `@default`(now())

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/docs/content/docs/orm/prisma-schema/overview/index.mdx` at line 17,
Update the createdAt field in the Prisma schema example to use the valid
case-sensitive DateTime scalar instead of datetime, matching the existing type
usage in the surrounding model.