The only way to hack around this would be to write a script to rename the models (and us @@map to keep the name consistent) then use a proxy to provide the correct table.
Misc
It looks like Prisma investigated separating tables by schema, but since deleted the GitHub comment: https://arc.net/l/quote/kuaashkx
Motivation
We currently need a separate Prisma client for each database schema. This requires a separate pool, which means more Postgres connections than needed.
Implementation
This is currently not yet possible.
Prisma now support multiple schemas, but the tables are in the same namespace: https://www.prisma.io/docs/orm/prisma-schema/data-model/multi-schema
The only way to hack around this would be to write a script to rename the models (and us
@@map
to keep the name consistent) then use a proxy to provide the correct table.Misc
It looks like Prisma investigated separating tables by schema, but since deleted the GitHub comment: https://arc.net/l/quote/kuaashkx