New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I want to create multiple schemas in prisma orm #349
Comments
Hello! Prisma currently only supports one single Prisma Schema file. However, there are ways to achieve more flexibility with managing multiple schemas within Prisma. One approach is to break up large schema files into smaller, more manageable ones. This can make it easier to work with and maintain the schema. You can split your schema into different files and then import them into your main schema file. Another approach is to use modular architecture, where each module has its own self-contained logic, including its own schema. This can help with organization and separation of concerns. Each module can have its own Prisma Schema file, and you can use them together in your application. You can find more information and examples on how to achieve these approaches in the Prisma documentation and the Prisma community forum. |
are there any other open issues in prisma repo regarding this? |
Yes, there are several open issues in the Prisma GitHub repository related to managing multiple schemas. Here are a few you might find useful:
You can find more related issues by searching the Prisma GitHub repository using keywords like "multiple schema" or "split schema". It's a good idea to check these issues periodically for any updates and to contribute your thoughts and suggestions if necessary. |
Prisma currently only supports one single Prisma Schema file. Developers want more flexibility for managing their Prisma Schema files.
Motivations:
breaking up large schema files to make them more manageable
flexible integration with certain architectures, i.e. each module has its own self-contained logic including its schema
The text was updated successfully, but these errors were encountered: