Allows arbitrary reporting on your ledger using easy-to-write SQL queries

The new de-facto for API testing your Rails application

Manage the mails you send from Rails.

This gem will help you to integrate PostgreSQL RLS to help you develop a great multitenancy application checkout the repository at https://github.com/Dandush03/pg_rls

PostgreSQL PL/pgSQL stored procedure code coverage

Failover for ActiveRecord and Redis

This gem provides a way to connect to AWS Redshift using the ruby-pg.

This plugin provides native PostgreSQL instrumentation for monitoring and metrics collection, including: service health, database connectivity, database locks, replication status, database size, `pg_stat_bgwriter` metrics, and more.

This plugin provides native PostgreSQL instrumentation for monitoring and metrics collection, including: service health, database connectivity, database locks, replication status, database size, `pg_stat_bgwriter` metrics, and more.

Allows Sequel to use ActiveRecord connection for database interaction.

sequel-annotate annotates Sequel models with schema information. By default, it includes information on columns, indexes, and foreign key constraints for the current table. On PostgreSQL, this includes more advanced information, including check constraints, triggers, comments, and foreign keys constraints for other tables that reference the current table.

simple_recommender offers item-based similarity recommendations for a Rails app using Postgres, using your existing ActiveRecord associations

Manage delta indexes via Resque for Thinking Sphinx

This extension provides an interface for the admin to upload new themes, publish it to the spree store, modify the theme layout accordingly and later download it.

Description of Connect.

Provides easy DSL integration between ActiveAdmin & state_machine

Save unnecessary round trips to the database

An ActiveRecord plugin providing a higher-level abstraction for SQL 'LIKE' queries

Gives ActiveRecord support for PostgreSQL's native inherited tables

From http://edgeguides.rubyonrails.org/active_record_migrations.html#types-of-schema-dumps: There is however a trade-off: db/schema.rb cannot express database specific items such as triggers, stored procedures or check constraints. While in a migration you can execute custom SQL statements, the schema dumper cannot reconstitute those statements from the database. If you are using features like this, then you should set the schema format to :sql. No longer is this the case. You can now use the default schema format (:ruby) and still preserve your check constraints.