online_migrations VS Scenic

Or simply use https://github.com/fatkodima/online_migrations and don’t get bitten by migrations in production again.

I would like to suggest for consideration a more feature-rich alternative to "strong_migrations" - https://github.com/fatkodima/online_migrations (there is a comparison with it in the README).

There is kinda such a linter, but for ruby/rails projects - https://github.com/fatkodima/online_migrations.

For other people looking into zero-downtime migrations: you may also consider easier to use ruby-based tool for this https://github.com/fatkodima/online_migrations

For ruby users, there is an existing gem that helps with this: https://github.com/fatkodima/online_migrations

Thanks for mentioning. I made a comparison with it - https://github.com/fatkodima/online_migrations#cool-but-ther...

To model our Deliverable class, we will need a view. We will use the popular scenic gem, which provides some useful generators for creating views with their respective migrations, and utilities to handle views versioning.

+1 for scenic - https://github.com/scenic-views/scenic

If the data doesn't need to be close to real-time, and if your DB can handle a bit of load, I'd use a "batch" approach. To do this, I'd create a materialized view in your relational DB that you'd then refresh periodically. The easiest way to do this is with the `scenic` gem. Once you've done this, you can simply create a new model and set the `table_name` to the name of the materialized view, and then treat it as a regular model.

I use the scenic gem to manage views which uses raw sql files: https://github.com/scenic-views/scenic

add scenic

TIL about fx gem for storing triggers in schema.rb. That makes me so happy because scenic gem for creating database views is one of my favorites. Postgres is very powerful and it's great to see tools for exposing that through Rails.