Hello! I am very interested in adding Prisma to the stack we are using for a commercial web application. After reviewing the documentation and an open GitHub ticket: https://github.com/prisma/prisma/issues/1122... it looks as though you can only add a single schema to Prisma's configuration? We have customer data separated by schemas within a singular db, and need to know if your solution will allow us to be able to build queries that point to different schemas. No cross-schema joins or anything like that is necessary, we only need to execute queries within the same schema. Any insight or guidance would be greatly appreciated.

Hi @Ryan Roline! Even though this isn't fully supported yet by Prisma, my utility CLI Prisma Util has support for this, along with cross-file relations. Let me know if you need any help.

Hi @Ryan Roline 👋 We do have support for this feature in early access as can be seen on the roadmap here. In order to help us understand your usecase better, Could you describe your technical stack, like the programming language, automation tooling, hosting, and cloud providers you use?

Thank you @Raphael Etim and @David Hancu for the quick replies. We are using a MERN stack (Mongo, Express, React, Node) with our client data on a CockraochDB server. For security reasons, we use schemas to separate client access to our database to prevent any cross contamination. It is critical for us to have the ability to dynamically build queries that hit different schemas in order to retrieve data through our API. We would also like to be able to do so with only a single Prisma connection. Hopefully that adds a little clarity to our situation. Do the planned changes cater to these needs?

👋 Hello @Ryan Roline thank you for the additional context and information! I've shared it with the Product team and we'll get back to you asap on your roadmap question!