Relational db to ActiveREcord models MAPper

Ruby Amazon Web Services Cloud Search Interface

Active Record caching and indexing in memcache.

RecordFilter is a Pure-ruby criteria API for building complex queries in ActiveRecord. It supports queries that are built on the fly as well as named filters that can be added to objects and chained to create complex queries. It also gets rid of the nasty hard-coded SQL that shows up in most ActiveRecord code with a clean API that makes queries simple and intuitive to build.

Recursively delete all dependent model associations without an N + 1

Adds support in ActiveRecord for foreign_keys, complex indexes and other database-related stuff. Easily create foreign_keys, complex indexes and views.

Dump statistics from Redis to DB

Store application and user settings on Redis. Comes with ActiveRecord support.

Return struct results from ActiveRecord relation queries

Admin interface for RubyOnRails projects inspired by Leaf CMS

A collection of RSpec matchers for web apps.

Rescues unique constraint violations and turns them into ActiveRecord errors

Provides a relational feature to your Rails application.

This gem provides two-way bindings between Salesforce records and records in an ActiveRecord-compatible database. It leans on the Restforce library for Salesforce API interactions, and provides a self-daemonizing binary which keeps records in sync by way of a tight polling loop.

Model serialization, paging, side-loading and filtering

Adds several handy expectations for testing ActiveRecord model validations, similar to what Shoulda provides.

Provide a language server implementation for ruby in ruby. See https://microsoft.github.io/language-server-protocol/ "A Language Server is meant to provide the language-specific smarts and communicate with development tools over a protocol that enables inter-process communication."

Converts to/from date & time inputs for managing scheduled models.

SchemaAssociations extends ActiveRecord to automatically create associations by inspecting the database schema. This is more more DRY than the standard behavior, for which in addition to specifying the foreign key in the migration, you must also specify complementary associations in two model files (e.g. a :belongs_to and a :has_many).

schema_comments generates extra methods dynamically for attribute which has options.