Project

Reverse Dependencies for activerecord

The projects listed here declare activerecord as a runtime or development dependency

0.0
No release in over 3 years
active_record-pool is an extension to active_record that gives you an interface to write high-speed inserts, updates, & delete in a manageable way.
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
A Rails database adapter that gives each git branch its own Postgres schema. Migrations run in isolation. Nobody steps on anyone else's work.
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
PostgreSQL allows to create a procedure which returns a result set. The gem modifies ActiveRecord so that it's possible to create (readonly) model based on resultset instead of a database table.
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
This gem provides a patch that once included will retry the PostgreSQL operation in case the server has gone away
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
Recovers from stale ActiveRecord PostgreSQL connections after AWS RDS or Aurora failover, deploys, restarts, and network interruptions by retrying safe reads, clearing pools, and reporting recovery events.
2021
2022
2023
2024
2025
2026
0.0
No release in over 3 years
Adds support for PostgreSQL 128 bit UUID column type to ActiveRecord
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
At deploy time, activerecord-precompiled rewrites simple ActiveRecord query chains in your application source (e.g. `User.where(name: n).first`) into direct calls on the SQLite3 raw connection with SQL generated by ActiveRecord itself. The original expression is kept as a fallback for any case th...
2021
2022
2023
2024
2025
2026
0.0
No release in over a year
ActiveRecordPrettyKey provides functionality to generate and manage pretty, human-readable keys for ActiveRecord models.
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
Store model settings and properties in JSONB columns with a clean DSL, type casting, default values, and validations. A modern alternative to separate settings tables.
2021
2022
2023
2024
2025
2026