active_record_doctor
Scenic
Our great sponsors
active_record_doctor | Scenic | |
---|---|---|
4 | 8 | |
1,626 | 3,338 | |
- | 1.0% | |
6.9 | 4.1 | |
27 days ago | 15 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
active_record_doctor
-
Many of us can face issues working with ActiveRecord due to its inconsistency with the database schema. That's why I have built database_consistency, which can help you avoid the most common issues and improve your application's performance.
Thank you for your contribution! How would you compare this gem to https://github.com/gregnavis/active_record_doctor?
-
Troubleshooting a RoR Application in Production
Start with finding mixing indexes: https://github.com/gregnavis/active_record_doctor
-
Windmill.dev
What did you build the website with? It looks really nice and I’m looking for something I could use with my project. [1]
[1] https://github.com/gregnavis/active_record_doctor
-
15 Resources I Learned Something From This Weekend
gregnavis / active_record_doctor
Scenic
-
Database Views & Rails Active Record: defining new Model classes out of views
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.
-
Materialised views for serious performance gains
+1 for scenic - https://github.com/scenic-views/scenic
-
Most performant way to build an analytics dashboard from a relational database backend that only stores numeric values, where the data the end-user sees is "categorized" into numeric brackets (e.g. 60-79 = Med, 80-100 = High, etc)
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.
- Utilizando views SQL no Ruby on Rails
-
Frameworks for SQL Development in Rails?
I use the scenic gem to manage views which uses raw sql files: https://github.com/scenic-views/scenic
-
Rails application boilerplate for fast MVP development
add scenic
-
Logidze 1.0, postgres-specific alternative to eg paper_trail for recording ActiveRecord change history
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.
What are some alternatives?
Rails DB - Rails Database Viewer and SQL Query Runner
Lol DBA - lol_dba is a small package of rake tasks that scan your application models and displays a list of columns that probably should be indexed. Also, it can generate .sql migration scripts.
PgHero - A performance dashboard for Postgres
ActiveRecord::DataIntegrity - Check data integrity for your ActiveRecord models
SecondBase - Seamless second database integration for Rails.
Blazer - Business intelligence made simple
Polo - Polo travels through your database and creates sample snapshots so you can work with real world data in development.
prosopite - :mag: Rails N+1 queries auto-detection with zero false positives / false negatives
SchemaPlus - SchemaPlus provides a collection of enhancements and extensions to ActiveRecord
BatchLoader - :zap: Powerful tool for avoiding N+1 DB or HTTP queries
Ruby PG Extras - Ruby PostgreSQL database performance insights. Locks, index usage, buffer cache hit ratios, vacuum stats and more.