Skip to content
Discussion options

You must be logged in to vote

Alrighty, how I solved this shadow database issue of mine...

One part of the problem was migrate diff created a migration.sql file with UTF-8 with BOM encoding instead of just UTF-8.
I was able to pass through the 'baselining_dev_database' migration file after changing to UTF-8, but I came across a different shadow database error on some relations already existing.

Since I don't particularly care for the long-term tracking of changes in the database structure, I decided to delete all the records in the "_prisma_migrations" table in the database and removed the "/prisma/migrations" folder.

Started the "Baselining a database" steps all over again, and this time no issues on shadow database …

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Answer selected by exort-apps
Comment options

You must be logged in to vote
1 reply
@exort-apps
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants