pry-rails VS Scenic

There are a few options for this behavior. There is https://github.com/pry/pry-rails which allows you to set break points in your code that does exactly what you're describing when it's hit. Or there's https://github.com/BetterErrors/better_errors. This one does a pretty page when an error happens with a live console open on the page you can use.

Have you seen the pry-rails gem, it's really helpful if you want to see methods implementations and classes. You can set it as your default rails console. And you can combine it with pry.binding for better debugging

pry-rails and amazing_print for better rails console

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.