add note about prisma migrations in postgres-multi-schema

[lsmith77]

fixes zenstackhq/zenstack-v3#605

another option could be to automatically add the previewFeatures config to the schema.prisma if multiple schema are configured in PostgreSQL. this would be the cleaner option. see zenstackhq/zenstack-v3#613

Summary by CodeRabbit

• Documentation
  • Added PostgreSQL multi-schema guide with instructions for enabling Prisma Migrations in multi-schema setups, including configuration examples.

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

[vercel]

@lsmith77 is attempting to deploy a commit to the ZenStack Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

A new "Prisma Migrations" section is added to the PostgreSQL multi-schema guide, explaining how to enable multi-schema support by configuring the generator and plugin in schema.prisma.

Changes

Cohort / File(s)	Change Summary
Documentation: PostgreSQL Multi-Schema Migrations docs/recipe/postgres-multi-schema.md	Adds "Prisma Migrations" section with code examples showing generator configuration with multiSchema preview feature and plugin setup

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR adds documentation but does not address the core issue #605 requirement: preserving @@Schema() and datasource.schemas in schema.prisma generation.	Implement code changes to preserve @@Schema() attributes and datasource.schemas array during schema generation, not just add documentation.
Out of Scope Changes check	❓ Inconclusive	The documentation addition is narrowly scoped but tangential to the core functional requirement of preserving multi-schema configuration during generation.	Clarify whether this documentation-only PR is intended as a separate effort from the functional fix for issue #605, or if functional code changes are also expected.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: adding documentation about Prisma migrations for multi-schema PostgreSQL setups.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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 and usage tips.}