Preview feature feedback: Prisma multi schema support (`multiSchema`)
See original GitHub issueHere are details on how the preview feature for multi schema support currently works in Prisma: https://github.com/prisma/prisma/issues/1122#issuecomment-1231773471
Please share your feedback about the multiSchema
functionality released in v4.3.0 in this issue.
- If you encounter a bug, please open a bug report in this repo.
- If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue.
If you have any questions, don’t hesitate to ask them in the #prisma-client
channel in the Prisma Slack.
Issue Analytics
- State:
- Created a year ago
- Reactions:15
- Comments:18 (7 by maintainers)
Top Results From Across the Web
How to use Prisma with multiple database schemas
Multi -schema support is currently in preview. To enable the multiSchema preview feature, add the multiSchema feature flag to the previewFeatures field of ......
Read more >Prisma Client and Prisma schema preview features
When we release a new Prisma Client or Prisma schema feature, it often starts in preview so that you can test it and...
Read more >Upgrading to use Preview features (Guides) - Prisma
Preview features are new features that can only be used by opting in using a corresponding feature flag. Enabling preview features.
Read more >Referential actions - Prisma
Prisma support of referential actions removes the safety net in Prisma Client that prevents cascading deletes at runtime. If you use the feature...
Read more >What Prisma doesn't have yet - DEV Community
Tagged with prisma, webdev, discuss, opensource. ... Preview feature feedback: Prisma multi schema support (`multiSchema`) #15077.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This will work later @shaked420 - it is a known limitation right now. You will need give the models different names, and then use
@@schema
and@@map
to point to the correct schema and table for each. (Fields are not affected by this at all.)Well, not sure why you need to list the schemas in
datasource
. Just marking the models should be enough?