fix: do not use explicit shadow database #45

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

Jump to bottom

Closed

patrickhulce wants to merge 1 commit into vercel:main from patrickhulce:patch-1

Closed

fix: do not use explicit shadow database #45

patrickhulce wants to merge 1 commit into vercel:main from patrickhulce:patch-1

Conversation

patrickhulce

Copy link

@patrickhulce patrickhulce commented Oct 19, 2023

Removes the shadow database URL to fix the bugs once migrations are introduced.

See shadow database documentation and prisma/prisma#19234 (comment).

Important: Do not use the same values for directUrl and shadowDatabaseUrl.

@patrickhulce


 fix: do not use explicit shadow database

e18b462

Removes the shadow database URL to fix the bugs once migrations are introduced.
See [shadow database documentation](https://www.prisma.io/docs/concepts/components/prisma-migrate/shadow-database) and prisma/prisma#19234 (comment). 
> Important: Do not use the same values for directUrl and shadowDatabaseUrl.

@vercel

Copy link