Enumerize
Enumerated attributes with I18n and ActiveRecord/Mongoid support (by brainspec)
ActiveRecord Where Assoc
Make ActiveRecord do conditions on your associations (by MaxLap)
| Enumerize | ActiveRecord Where Assoc | |
|---|---|---|
| - | 8 | |
| 1,754 | 226 | |
| 0.5% | 1.3% | |
| 5.0 | 7.0 | |
| 24 days ago | 15 days ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
Enumerize
Posts with mentions or reviews of Enumerize.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning Enumerize yet.
Tracking mentions began in Dec 2020.
ActiveRecord Where Assoc
Posts with mentions or reviews of ActiveRecord Where Assoc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-29.
-
EXISTS clause for active record
I’ve been using the activerecord_where_assoc gem for this. I think it’s API is more natural than this proposal.
-
My new gem lets you follow associations when doing ActiveRecord queries. Here's an intro for follow_assoc.
Your examples using joins would return duplicated Sections. That might force you to add a distinct. I personally find it wrong to do a distinct in a scope just to be able to make the condition I want the scope to do. It's a hidden side effect that could cause problem elsewhere and it's unexpected from the name of the scope. I made a gem to deal with that situation: where_assoc. There is definitely an overlap between both gem.
-
Rails 6.1 adds query method associated to check for the association presence
Assuming that ... was indicating some form of annoyance with that distinct, you might want to take a look at activerecord_where_assoc
-
Rails 6.1.1 allows `where` to reference associations via joined table alias names.
For those interested, the example uses this gem: activerecord_where_assoc
-
Active Record: x.includes(y): y was not recognized for preload
Here is an introduction to the gem.
What are some alternatives?
When comparing Enumerize and ActiveRecord Where Assoc you can also consider the following projects:
Goldiloader - Just the right amount of Rails eager loading
activerecord_json_validator - 🔩 ActiveRecord::JSONValidator makes it easy to validate JSON attributes against a JSON schema.
ActiveRecord::Turntable - ActiveRecord Sharding Plugin
manyfold - A self-hosted digital asset manager for 3d print files.
Rails PG Extras - Rails PostgreSQL database performance insights. Locks, index usage, buffer cache hit ratios, vacuum stats and more.
ActsAsTree - ActsAsTree -- Extends ActiveRecord to add simple support for organizing items into parent–children relationships.