Annotate VS Scenic

gem "annotate" - https://github.com/ctran/annotate_models | Adds DB-schema comments to models. May be unnecessary on RubyMine, YMMW.

I believe Ctran is aware of this based on his response in this issue https://github.com/ctran/annotate_models/issues/913

A gem that's pretty useful alongside this one is the annotation gem -- it prefixes models with their specific schema dump (as comments) and then updates those descriptive comments on migration. It's one of my go-to gems to install when I rotate onto a new-to-me Rails project (or start a new one) and I'm working to understand the data model.

Have you looked at annotate for inspiration?

I get it, though. Sounds like you're used to seeing every column definition in there. And that would be handy. There is a gem that you might like: https://github.com/ctran/annotate_models

annotate for annotations

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.