strong_migrations

There's also https://github.com/ankane/strong_migrations for Ruby The checks/explanations are fairly simple and straightforward so it also makes a good reference regardless of whether you're using the library

Hey HN! We've been helping other companies build their AI code reviewers, and noticed that people ended up writing similar rules. So we built a directory for them! We've also compiled instructions for all the major code reviewers out there (Github Copilot, Coderabbit, Greptile, Diamond). The biggest thing we've done is port strong migrations (https://github.com/ankane/strong_migrations) to other languages and ORMs. If you've ever used ruby and miss strong migrations - well, you can have them now. We plan on keeping this up to date over time with more helpful rules. If you have any that you added to your code review process, please feel free to share and we can add it to the directory.

A thing I always go back to, regardless of what language I'm working in, is the checks performed by strong migrations https://github.com/ankane/strong_migrations?tab=readme-ov-fi... It's pretty popular, and has even been ported to other languages https://github.com/Artur-Sulej/excellent_migrations

Strong migrations helps writing migrations that are safe for ZDD deploys. We use it in our rails app, catches quite a few potential footguns. https://github.com/ankane/strong_migrations

Makes sense. Check out the implementation of automatic lock timeout retries in Strong Migrations. Lock Timeout Retries [experimental] https://github.com/ankane/strong_migrations

In the Rails world, the gem strong_migrations can be used to detect these: https://github.com/ankane/strong_migrations The docs include a handy articulation of fixes.

Semi related https://github.com/ankane/strong_migrations

Already existing gem works for both MySQL and PostgreSQL https://github.com/ankane/strong_migrations

Half of the problems in this article are migration related. I am extremely grateful that some people have created awesome libraries like strong migrations https://github.com/ankane/strong_migrations. Even if you are not using rails, you can bookmark its readme, it is an awesome cheat-sheet on how to do common database migrations.

There is already https://github.com/ankane/strong_migrations

I would suggest taking a look at strong migrations[1]. It's a rails project, but the readme does a great job explaining what it checks for and what safe alternative to use instead. I still link to their explanations in PRs for non-rails projects. The examples unfortunately use the Rails migration DSL instead of plain SQL. If anyone knows of a SQL-first reference, I'd love to hear about it. [1]: https://github.com/ankane/strong_migrations#checks

> Ecto prevents N+1 queries by default, which I think is clearly better. To be fair... If you want to protect yourself from these with Rails you can install Bullet[0] and get protection through in your face notifications, and you have the option to let it slide because you're taking advantage of caching with Rails and in this case you know what you're getting into and the N+1 query with caching ends up being better because you understand your domain. Rails also has the strong migrations[1] gem which is a huge help for not shooting yourself in the foot for running migrations in production by helping you avoid table locks and other issues / errors. But AFAIK there's no Ecto equivalent, but strong migrations is really really useful. Rails also has the data-migrate[2] gem which is a nice little abstraction for splitting out your schema change