with-prisma: multiple prisma clients / database failing example #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using Prisma with Turborepo works great when following https://turbo.build/repo/docs/handbook/tools/prisma if there is only one Prisma client in the repository.
However, when running Turborepo with multiple Prisma clients and databases they will overwrite each other. There are loads of hacks out there, some mentioned here prisma/prisma#10433 (comment) but no real solutions as far as I can tell.
I wanted to raise awareness of this here and maybe it is worth adding a caveat to the docs about this so users are aware. What do you think?