Skip to content
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

Add warning note for shadowDatabaseUrl. #4188

Merged
merged 1 commit into from Dec 14, 2022

Conversation

rmariuzzo
Copy link
Contributor

Describe this PR

As a developer I made the mistake to put the same value for both url and shadowDatabaseUrl. This lead to situation where the Prisma's migration table disappeared several times resulting in an inconsistent app state.

Changes

  • Added a note.

What issue does this fix?

Can be useful for other devs.

Any other relevant information

Probably, we could expand and tell concisely what happens when we put the same value.

As a developer I made the mistake to put the same value for both `url` and `shadowDatabaseUrl`. This lead to situation where the Prisma's migration table disappeared several times resulting in an inconsistent app state.
@vercel
Copy link

vercel bot commented Dec 5, 2022

@rmariuzzo is attempting to deploy a commit to the Prisma Team on Vercel.

A member of the Team first needs to authorize it.

@janpio
Copy link
Member

janpio commented Dec 5, 2022

I created an issue that we actually forbid that, so we will not need that warning when this is implemented: prisma/prisma#16628

@vercel
Copy link

vercel bot commented Dec 14, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
docs ❌ Failed (Inspect) Dec 14, 2022 at 10:59AM (UTC)

@andrew-walford-prisma
Copy link
Contributor

Even though we're going to fix the issue in the product, I've merged this docs PR, so that this information is available in the interrim. Thans @rmariuzzo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants