Hello! We've got a use case where our database schema has to be changed. But those changes can't be executed without resetting the. However, resetting the production database isn't our plan 🙂 Was going through this thread: https://github.com/prisma/prisma/discussions/10031 This thread is still unanswered. RedwoodJS is not something we're using. hence we're looking for some sort of standalone solution. Does anyone have any leads on this front? Any help would be appreciated. Thanks!

Hi @Kinjal Raykarmakar - when you create a migration then it creates standard sql files in the

prisma/migrations

directory. You can now edit the files before you run the migration. Could you possibly do this to "work around" the need to "reset" the production database?

Hey @Richard Ward, thanks for replying. We thought of doing so, but there would result in a huge amount of raw SQL required to be written. Do you suggest any other ways or tools to accomplish this instead of modifying the migration file?

Hey Kinjal 👋 What is your exact use case? Is it the same as described in the GitHub Issue you have linked? Just to check, for the database that cannot be reset did you had a look at baselining?