occams-record
Scenic
| occams-record | Scenic | |
|---|---|---|
| 4 | 8 | |
| 355 | 3,341 | |
| - | 0.6% | |
| 7.4 | 5.8 | |
| 22 days ago | 27 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.
occams-record
- ORMs are criticized for the wrong reasons
- Use PG cursors (and more!) in Rails with occams-record 1.4.0
- Rails Pros - Help dispel some misconceptions and confusion for me
-
“Yeah, we’re a pretty modern company here”
Active record is a memory hog and Easily lets you fall into N+1 problems. Shout out to my buddy’s library that helps solve these problems for read queries, https://github.com/jhollinger/occams-record
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?
active_record_doctor - Identify database issues before they hit production.
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.
ActiveRecord Setops - Union, Intersect, and Difference set operations for ActiveRecord (also, SQL's UnionAll).
PgHero - A performance dashboard for Postgres
SQL Server - SQL Server Adapter For Rails
SecondBase - Seamless second database integration for Rails.
ransack - Object-based searching.
Polo - Polo travels through your database and creates sample snapshots so you can work with real world data in development.
SchemaPlus - SchemaPlus provides a collection of enhancements and extensions to ActiveRecord
Ruby PG Extras - Ruby PostgreSQL database performance insights. Locks, index usage, buffer cache hit ratios, vacuum stats and more.
Database Cleaner - Strategies for cleaning databases in Ruby. Can be used to ensure a clean state for testing.
BatchLoader - :zap: Powerful tool for avoiding N+1 DB or HTTP queries