-
Notifications
You must be signed in to change notification settings - Fork 990
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
Mitigate confusion and errors resulting from Prisma's Shadow DB 😈 #2091
Comments
@thedavidprice I hardly remembered that the shadow db is a thing. Do you think this is still a concern? |
@thedavidprice I'm going to close this one but feel free to re-open if you think we should address this for v1. |
@jtoar Re-opening this one — I'd like us to first audit the experience in the case where:
What happens? And is the resulting error clear about needing a second DB and how to set it up? If the experience is adequate, then I'd say let's close it out. |
We get the following error :
The Prisma doc give a workaround by creating a dedicate shadow database from a cloud-hosted DB,
@thedavidprice I think the experience is adequate, we can maybe still add it to our doc as a head-up somewhere in this part : https://redwoodjs.com/docs/deploy/introduction#3-prisma-and-database |
Latest example of this is #5767. |
I'm seeing more questions, issues, and errors resulting from confusion about Prisma Migrate's new Shadow DB. (Additionally, we have some similar confusion regarding Redwood's local Test DB requirements in case of switching off SQLite).
For context, see my answer to Thomas in the Forums: https://community.redwoodjs.com/t/creating-a-startup-support-crew/1805/38
Questions/Ideas
Update
Help wanted --> see this comment re: next step auditing the current experience.
The text was updated successfully, but these errors were encountered: