Run a migration by hand and update the migration table manually
See original GitHub issueProblem
Adding indexes should be done concurrently in postgres
Prisma generates indexes in the migration.
Indexes concurrently can’t be added in a transaction
I run the migration manually by hand and comment out the add indexes while running prisma migrate deploy
Afterwards Prisma deploy will say
WARNING The following migrations have been modified since they were applied:
Suggested solution
One solution could be:
Output the checksum so that I can update it manually
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Code First Migrations - EF6 - Microsoft Learn
Let's use Update-Database to apply this migration to the database. Run the Update-Database command in Package Manager Console; Code First ...
Read more >How to Run a Django Migration “By Hand” - Adam Johnson
Normally your Django project's deploy process runs the migrate command, and that takes care of updating your database as necessary.
Read more >Create a Migration in Rails Manually | by Shaqqour - Medium
Migration in Rails is responsible for creating and editing database tables. To migrate the database changes in rails, run $ rails db:migrate.
Read more >Migrations
Rails 3.1 makes migrations smarter by providing a new change method. This method is preferred for writing constructive migrations (adding columns or tables)....
Read more >how to re-migrate a laravel migration after deleting the table
Laravel keeps a record of migrations that have been run. You need to go to the migrations table and delete the migration record....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the update. That feature would really help with databases that have tables with millions of rows with a lot of traffic, as creating an index with locking is not feasible.
Everything that is not supported is on the roadmap - the question is when exactly. Right now
CREATE INDEX CONCURRENTLY
is not super high on that list as we have more basic functionality (see feature requests).