I've been digging into database migrations, especially for Postgres and MySQL, and I'm curious to see what others are using in real projects. What tools or ORMs are you currently using for migrations? Options like Prisma, Sequelize, TypeORM, Knex, Flyway, and Liquibase come to mind. I've noticed some quirks: for instance, Flyway and Liquibase don't actually generate migrations, they just execute them. On the flip side, ORMs usually generate migrations but can have their own issues, like Sequelize not properly altering certain Postgres types or Prisma dropping and recreating columns when they're renamed. If you could create a database migration system from scratch, what changes would you want to see? What are the major pain points or things you feel are missing? Would love to hear your thoughts!
6 Answers
Entity Framework is my go-to for migrations in .NET. It's super simple since it automatically generates both up and down migrations. I've had no issues with it so far—just works!
Totally second that! I've used EF for a couple of years now and it's been smooth sailing. Just double-check the auto-generated migrations occasionally.
Django is, without a doubt, the best for handling migrations. It’s incredibly safe and well-documented, plus you get to avoid a lot of pitfalls that come with other tools!
If you’re using Golang, I’d recommend Goose. It’s quite straightforward for managing migrations and fits well with raw SQL if that's your thing.
I find it interesting how divided opinions are between sticking with robust frameworks like EF/Django versus going completely raw SQL. I've often wished for a tool that can handle messy schemas well—something that can accurately detect complex differences without misinterpretations. These auto-generated migrations can lead to unintended side effects really quickly! Does anyone here trust their migration setups enough to let them run unattended in CI?
Good question! I still review changes manually before they go live. It's too risky to trust auto-generated migrations completely.
I run CI for migration tests but still check them all manually. You never know when a rename will turn into a drop-and-recreate mess!
I use Prisma wherever I can, especially since it has handy built-in functions. For other projects, I default to Flyway, but I also consider the prior developer’s choices. Remember, it's okay to tweak generated migrations if needed. For example, Prisma might handle renames differently, but you can always customize the migration afterward. It's more about how well you apply the changes than how they’re generated!
Exactly! It's crucial to understand that migration tools are helpers. You'll often need to tailor them to fit your project's specific needs, especially in complex scenarios.
Honestly, I stick to raw SQL for everything. I haven’t had any issues that would necessitate the overhead of additional tools. It's straightforward and gets the job done!
I agree! EF is awesome, though I have my gripes with some other Microsoft stuff. But when it comes to migrations, EF really shines.