paper_trail 5.0.1 → 5.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9cd678385e88cdbf152ecc4c2a4a1876afd7a175
-  data.tar.gz: 93e28bbba83f8be22cfb8db3ee3e1912818f86af
+  metadata.gz: 83f408e34bbaf733c5fdab5ad37fc8c3718ab7ad
+  data.tar.gz: b1e73feb664e29d18946f3c526b1bb6b1ccec024
 SHA512:
-  metadata.gz: 19a6e0288279964bced8ca4d4ae4ccacd668e1750dbff133d8c6e3ee76514c150402669c808954b24efcfb0fa085b370e3c20d2afe667bd4385d4ea233f4449e
-  data.tar.gz: b26460e5948b60afb39fc6dc18c04f7c3337d449dc8a0401efc67d3cdabaa193fd3f23341d8d4f44f8ed726af4e5f81079d7be24372b3a6d8dbae683d852e44b
+  metadata.gz: b61edd25675bb0ea5254640920f04ff23aab1fc9dc729bc2bb27c5f4bd6774fb6e86df50d213d173a2892e7b2ef2e15240745e541d9f4fb0238c4b07574f6e56
+  data.tar.gz: 8b701f3921a8945fd3e7e55dbda82c7b716711e457f72caf7054dd502fd77a927ef5c5ebcf7d634f9c8465ba0bc8c44cc057220bea24cbaac1f5dbad7f2c9a96

data/.github/CONTRIBUTING.md

@@ -96,7 +96,8 @@ DB=postgres bundle exec rake
 1. In the readme,
   - remove "unreleased" from the doc versions table
   - update any other references to version number
-1. Commit and tag with `git tag -a -m "v5.0.0" "v5.0.0"`
+1. Commit
+1. Tag with `git tag -a -m "v5.0.0" "v5.0.0"`
 1. `git push --tags origin master`
 1. `gem build paper_trail.gemspec`
 1. `gem push paper_trail-5.0.0.gem`

data/.github/ISSUE_TEMPLATE.md

@@ -8,6 +8,6 @@ Please use our template
 when reporting bugs.
 
 For other questions, please see our contributing guide.
-(https://github.com/airblade/paper_trail/blob/master/.github/CONTRIBUTING.MD)
+(https://github.com/airblade/paper_trail/blob/master/.github/CONTRIBUTING.md)
 
 Thanks for your contribution!

data/.rubocop_todo.yml

@@ -8,7 +8,7 @@ Metrics/CyclomaticComplexity:
   Max: 13 # Goal: 6
 
 Metrics/ModuleLength:
-  Max: 299
+  Max: 313
 
 Metrics/PerceivedComplexity:
   Max: 16 # Goal: 7

data/Appraisals

@@ -2,7 +2,7 @@
 # `paper_trail.gemspec`.
 #
 # > The dependencies in your Appraisals file are combined with dependencies in
-# > your Gemfile, so you don"t need to repeat anything that"s the same for each
+# > your Gemfile, so you don't need to repeat anything that's the same for each
 # > appraisal. If something is specified in both the Gemfile and an appraisal,
 # > the version from the appraisal takes precedence.
 # > https://github.com/thoughtbot/appraisal
@@ -26,15 +26,11 @@ appraise "ar4" do
 end
 
 appraise "ar5" do
-  gem "activerecord", "5.0.0.beta1"
-  gem "activemodel", "5.0.0.beta1"
-  gem "actionpack", "5.0.0.beta1"
-  gem "railties", "5.0.0.beta1"
-  gem "rspec-rails", github: "rspec/rspec-rails"
-  gem "rspec-core", github: "rspec/rspec-core"
-  gem "rspec-expectations", github: "rspec/rspec-expectations"
-  gem "rspec-mocks", github: "rspec/rspec-mocks"
-  gem "rspec-support", github: "rspec/rspec-support"
+  gem "activerecord", "5.0.0.beta3"
+  gem "activemodel", "5.0.0.beta3"
+  gem "actionpack", "5.0.0.beta3"
+  gem "railties", "5.0.0.beta3"
+  gem "rspec-rails", "3.5.0.beta3"
   gem 'rails-controller-testing'
   # Sinatra stable conflicts with AR5's rack dependency
   gem 'sinatra', github: 'sinatra/sinatra'

data/CHANGELOG.md

@@ -1,3 +1,36 @@
+## 5.?.? (Unreleased)
+
+### Breaking Changes
+
+- None
+
+### Added
+
+- None
+
+### Fixed
+
+- None
+
+## 5.1.0 (2016-05-20)
+
+### Breaking Changes
+
+- None
+
+### Added
+
+- [#809](https://github.com/airblade/paper_trail/pull/809) -
+  Print warning if version cannot be saved.
+
+### Fixed
+
+- [#812](https://github.com/airblade/paper_trail/pull/812) -
+  Issue with saving HABTM associated objects using accepts_nested_attributes_for
+- [#811](https://github.com/airblade/paper_trail/pull/811) -
+  Avoid unnecessary query in #record_destroy
+- Improvements to documentation
+
 ## 5.0.1 (2016-05-04)
 
 ### Breaking Changes

data/README.md

@@ -19,34 +19,39 @@ has been destroyed.
 
 ## Table of Contents
 
-- [Compatibility](#compatibility)
-- [Installation](#installation)
-- [Basic Usage](#basic-usage)
-- [API Summary](#api-summary)
-- Limiting What is Versioned, and When
-  - [Choosing Lifecycle Events To Monitor](#choosing-lifecycle-events-to-monitor)
-  - [Choosing When To Save New Versions](#choosing-when-to-save-new-versions)
-  - [Choosing Attributes To Monitor](#choosing-attributes-to-monitor)
-  - [Turning PaperTrail Off](#turning-papertrail-off)
-  - [Limiting the Number of Versions Created](#limiting-the-number-of-versions-created)
-- Working With Versions
-  - [Reverting And Undeleting A Model](#reverting-and-undeleting-a-model)
-  - [Navigating Versions](#navigating-versions)
-  - [Diffing Versions](#diffing-versions)
-  - [Deleting Old Versions](#deleting-old-versions)
-- Saving More Information About Versions
-  - [Finding Out Who Was Responsible For A Change](#finding-out-who-was-responsible-for-a-change)
-  - [Associations](#associations)
-  - [Storing metadata](#storing-metadata)
-- ActiveRecord
-  - [Single Table Inheritance](#single-table-tnheritance)
-- Extensibility
-  - [Custom Version Classes](#custom-version-classes)
-  - [Custom Serializer](#custom-serializer)
-- [Testing](#testing)
-- [Sinatra](#sinatra)
-
-## Compatibility
+- [1. Introduction](#1-introduction)
+  - [1.a. Compatibility](#1a-compatibility)
+  - [1.b. Installation](#1b-installation)
+  - [1.c. Basic Usage](#1c-basic-usage)
+  - [1.d. API Summary](#1d-api-summary)
+- [2. Limiting What is Versioned, and When](#2-limiting-what-is-versioned-and-when)
+  - [2.a. Choosing Lifecycle Events To Monitor](#2a-choosing-lifecycle-events-to-monitor)
+  - [2.b. Choosing When To Save New Versions](#2b-choosing-when-to-save-new-versions)
+  - [2.c. Choosing Attributes To Monitor](#2c-choosing-attributes-to-monitor)
+  - [2.d. Turning PaperTrail Off](#2d-turning-papertrail-off)
+  - [2.e. Limiting the Number of Versions Created](#2e-limiting-the-number-of-versions-created)
+- [3. Working With Versions](#3-working-with-versions)
+  - [3.a. Reverting And Undeleting A Model](#3a-reverting-and-undeleting-a-model)
+  - [3.b. Navigating Versions](#3b-navigating-versions)
+  - [3.c. Diffing Versions](#3c-diffing-versions)
+  - [3.d. Deleting Old Versions](#3d-deleting-old-versions)
+- [4. Saving More Information About Versions](#4-saving-more-information-about-versions)
+  - [4.a. Finding Out Who Was Responsible For A Change](#4a-finding-out-who-was-responsible-for-a-change)
+  - [4.b. Associations](#4b-associations)
+  - [4.c. Storing metadata](#4c-storing-metadata)
+- [5. ActiveRecord](#5-activerecord)
+  - [5.a. Single Table Inheritance](#5a-single-table-inheritance-sti)
+  - [5.b. Configuring the `versions` Association](#5b-configuring-the-versions-association)
+  - [5.c. Generators](#5c-generators)
+- [6. Extensibility](#6-extensibility)
+  - [6.a. Custom Version Classes](#6a-custom-version-classes)
+  - [6.b. Custom Serializer](#6b-custom-serializer)
+- [7. Testing](#7-testing)
+- [8. Sinatra](#8-sinatra)
+
+## 1. Introduction
+
+### 1.a. Compatibility
 
 | paper_trail    | branch     | tags   | ruby     | activerecord |
 | -------------- | ---------- | ------ | -------- | ------------ |
@@ -56,7 +61,7 @@ has been destroyed.
 | 2              | 2.7-stable | v2.x   | >= 1.8.7 | >= 3.0, < 4  |
 | 1              | rails2     | v1.x   | >= 1.8.7 | >= 2.3, < 3  |
 
-## Installation
+### 1.b. Installation
 
 1. Add PaperTrail to your `Gemfile`.
 
@@ -70,7 +75,8 @@ has been destroyed.
     ```
 
     If using [rails_admin][38], you must enable the experimental
-    [Associations](#associations) feature.
+    [Associations](#associations) feature. For more information on this
+    generator, see [section 5.c. Generators](#5c-generators).
 
 1. Add `has_paper_trail` to the models you want to track.
 
@@ -90,7 +96,7 @@ by adding a controller callback.
     end
     ```
 
-## Basic Usage
+### 1.c. Basic Usage
 
 Your models now have a `versions` method which returns the "paper trail" of
 changes to your model.
@@ -146,7 +152,7 @@ Here's a helpful table showing what PaperTrail stores:
 PaperTrail stores the values in the Model Before column.  Most other
 auditing/versioning plugins store the After column.
 
-## API Summary
+### 1.d. API Summary
 
 When you declare `has_paper_trail` in your model, you get these methods:
 
@@ -156,7 +162,7 @@ class Widget < ActiveRecord::Base
 end
 
 # Returns this widget's versions.  You can customise the name of the
-# association.
+# association, but overriding this method is not supported.
 widget.versions
 
 # Return the version this widget was reified from, or nil if it is live.
@@ -226,13 +232,11 @@ version.index
 # Returns the event that caused this version (create|update|destroy).
 version.event
 
-# Query versions objects by attributes.
+# Query the `versions.object` column (or `object_changes` column), by
+# attributes, using the SQL LIKE operator. Known issue: inconsistent results for
+# numeric values due to limitations of SQL wildcard matchers against the
+# serialized objects.
 PaperTrail::Version.where_object(attr1: val1, attr2: val2)
-
-# Query versions object_changes field by attributes (requires
-# `object_changes` column on versions table).
-# Also can't guarantee consistent query results for numeric values
-# due to limitations of SQL wildcard matchers against the serialized objects.
 PaperTrail::Version.where_object_changes(attr1: val1)
 ```
 
@@ -248,7 +252,9 @@ user_for_paper_trail
 info_for_paper_trail
 ```
 
-## Choosing Lifecycle Events To Monitor
+## 2. Limiting What is Versioned, and When
+
+### 2.a. Choosing Lifecycle Events To Monitor
 
 You can choose which events to track with the `on` option.  For example, to
 ignore `create` events:
@@ -283,7 +289,7 @@ a.versions.size                           # 3
 a.versions.last.event                     # 'update'
 ```
 
-### Controlling the Order of AR Callbacks
+#### Controlling the Order of AR Callbacks
 
 The `has_paper_trail` method installs AR callbacks. If you need to control
 their order, use the `paper_trail_on_*` methods.
@@ -307,7 +313,7 @@ The `paper_trail_on_destroy` method can be further configured to happen
 `:after`. In PaperTrail 5, the default will be `:before`, to support
 ActiveRecord 5. (see https://github.com/airblade/paper_trail/pull/683)
 
-## Choosing When To Save New Versions
+### 2.b. Choosing When To Save New Versions
 
 You can choose the conditions when to add new versions with the `if` and
 `unless` options. For example, to save versions only for US non-draft
@@ -320,13 +326,13 @@ class Translation < ActiveRecord::Base
 end
 ```
 
-### Choosing Based on Changed Attributes
+#### Choosing Based on Changed Attributes
 
 Starting with PaperTrail 4.0, versions are saved during an after-callback. If
 you decide whether to save a new version based on changed attributes, please
 use attribute_name_was instead of attribute_name.
 
-## Choosing Attributes To Monitor
+### 2.c. Choosing Attributes To Monitor
 
 You can ignore changes to certain attributes like this:
 
@@ -413,11 +419,11 @@ class Article < ActiveRecord::Base
 end
 ```
 
-## Turning PaperTrail Off
+### 2.d. Turning PaperTrail Off
 
 PaperTrail is on by default, but sometimes you don't want to record versions.
 
-### Per Process
+#### Per Process
 
 Turn PaperTrail off for all threads in a `ruby` process.
 
@@ -434,7 +440,7 @@ There is also a rails config option that does the same thing.
 config.paper_trail.enabled = false
 ```
 
-### Per Request
+#### Per Request
 
 Add a `paper_trail_enabled_for_controller` method to your controller.
 
@@ -446,14 +452,14 @@ class ApplicationController < ActionController::Base
 end
 ```
 
-### Per Class
+#### Per Class
 
 ```ruby
 Widget.paper_trail_off!
 Widget.paper_trail_on!
 ```
 
-### Per Method
+#### Per Method
 
 You can call a method without creating a new version using `without_versioning`.
  It takes either a method name as a symbol:
@@ -470,7 +476,7 @@ Or a block:
 end
 ```
 
-## Limiting the Number of Versions Created
+### 2.e. Limiting the Number of Versions Created
 
 Configure `version_limit` to cap the number of versions saved per record. This
 does not apply to `create` events.
@@ -482,7 +488,9 @@ PaperTrail.config.version_limit = 3
 PaperTrail.config.version_limit = nil
 ```
 
-## Reverting And Undeleting A Model
+## 3. Working With Versions
+
+### 3.a. Reverting And Undeleting A Model
 
 PaperTrail makes reverting to a previous version easy:
 
@@ -519,7 +527,7 @@ You could even use PaperTrail to implement an undo system, [Ryan Bates has!][3]
 If your model uses [optimistic locking][1] don't forget to [increment your
 `lock_version`][2] before saving or you'll get a `StaleObjectError`.
 
-## Navigating Versions
+### 3.b. Navigating Versions
 
 You can call `previous_version` and `next_version` on an item to get it as it
 was/became.  Note that these methods reify the item for you.
@@ -575,7 +583,7 @@ And you can perform `WHERE` queries for object versions based on attributes:
 PaperTrail::Version.where_object(content: "Hello", title: "Article")
 ```
 
-## Diffing Versions
+### 3.c. Diffing Versions
 
 There are two scenarios: diffing adjacent versions and diffing non-adjacent
 versions.
@@ -640,7 +648,7 @@ If you wish to selectively record changes for some models but not others you
 can opt out of recording changes by passing `:save_changes => false` to your
 `has_paper_trail` method declaration.
 
-## Deleting Old Versions
+### 3.d. Deleting Old Versions
 
 Over time your `versions` table will grow to an unwieldy size.  Because each
 version is self-contained (see the Diffing section above for more) you can
@@ -654,7 +662,9 @@ sql> delete from versions where created_at < 2010-06-01;
 PaperTrail::Version.delete_all ["created_at < ?", 1.week.ago]
 ```
 
-## Finding Out Who Was Responsible For A Change
+## 4. Saving More Information About Versions
+
+### 4.a. Finding Out Who Was Responsible For A Change
 
 Set `PaperTrail.whodunnit=`, and that value will be stored in the version's
 `whodunnit` column.
@@ -732,12 +742,12 @@ last_version.paper_trail_originator         # 'Alice'
 last_version.terminator                     # 'Bob'
 ```
 
-### Storing an ActiveRecord globalid in whodunnit
+#### Storing an ActiveRecord globalid in whodunnit
 
 If you would like `whodunnit` to return an `ActiveRecord` object instead of a
 string, please try the [paper_trail-globalid][37] gem.
 
-## Associations
+### 4.b. Associations
 
 **Experimental feature**, see caveats below.
 
@@ -843,7 +853,7 @@ widget.reload.wotsit                             # nil
    rails until ActiveRecord 4.2 (https://github.com/rails/rails/pull/14359).
 1. PaperTrail can't restore an association properly if the association record
    can be updated to replace its parent model (by replacing the foreign key)
-1. Currently PaperTrail only support single `version_associations` table. The
+1. Currently PaperTrail only supports a single `version_associations` table. The
    implication is that you can only use a single table to store the versions for
    all related models. Sorry for those who use multiple version tables.
 1. PaperTrail only reifies the first level of associations, i.e., it does not
@@ -916,7 +926,7 @@ end
 
 See [issue 113][16] for a discussion about this.
 
-## Storing Metadata
+### 4.c. Storing Metadata
 
 You can store arbitrary model-level metadata alongside each version like this:
 
@@ -936,7 +946,7 @@ PaperTrail will call your proc with the current article and store the result in
 the `author_id` column of the `versions` table.
 Don't forget to add any such columns to your `versions` table.
 
-### Advantages of Metadata
+#### Advantages of Metadata
 
 Why would you do this?  In this example, `author_id` is an attribute of
 `Article` and PaperTrail will store it anyway in a serialized form in the
@@ -950,7 +960,7 @@ those versions you want:
 PaperTrail::Version.where(:author_id => author_id)
 ```
 
-### Metadata from Controllers
+#### Metadata from Controllers
 
 You can also store any information you like from your controller.  Override
 the `info_for_paper_trail` method in your controller to return a hash whose keys
@@ -964,7 +974,7 @@ class ApplicationController
 end
 ```
 
-### Protected Attributes and Metadata
+#### Protected Attributes and Metadata
 
 If you are using rails 3 or the [protected_attributes][17] gem you must declare
 your metadata columns to be `attr_accessible`.
@@ -982,7 +992,9 @@ end
 If you're using [strong_parameters][18] instead of [protected_attributes][17]
 then there is no need to use `attr_accessible`.
 
-## Single Table Inheritance (STI)
+## 5. ActiveRecord
+
+### 5.a. Single Table Inheritance (STI)
 
 PaperTrail supports [Single Table Inheritance][39], and even supports an
 un-versioned base model, as of 23ffbdc7e1.
@@ -999,7 +1011,50 @@ end
 However, there is a known issue when reifying [associations](#associations),
 see https://github.com/airblade/paper_trail/issues/594
 
-## Custom Version Classes
+### 5.b. Configuring the `versions` Association
+
+You may configure the name of the `versions` association by passing
+a different name to `has_paper_trail`.
+
+```ruby
+class Post < ActiveRecord::Base
+  has_paper_trail class_name: 'Version', versions: :drafts
+end
+
+Post.new.versions # => NoMethodError
+```
+
+Overriding (instead of configuring) the `versions` method is not supported.
+Overriding associations is not recommended in general.
+
+### 5.c. Generators
+
+PaperTrail has one generator, `paper_trail:install`. It writes, but does not
+run, a migration file. This migration adds (at least) the `versions` table. The
+most up-to-date documentation for this generator can be found by running `rails
+generate paper_trail:install --help`, but a copy is included here for
+convenience.
+
+```
+Usage:
+  rails generate paper_trail:install [options]
+
+Options:
+  [--with-changes], [--no-with-changes]            # Store changeset (diff) with each version
+  [--with-associations], [--no-with-associations]  # Store transactional IDs to support association restoration
+
+Runtime options:
+  -f, [--force]                    # Overwrite files that already exist
+  -p, [--pretend], [--no-pretend]  # Run but do not make any changes
+  -q, [--quiet], [--no-quiet]      # Suppress status output
+  -s, [--skip], [--no-skip]        # Skip files that already exist
+
+Generates (but does not run) a migration to add a versions table.
+```
+
+## 6. Extensibility
+
+### 6.a. Custom Version Classes
 
 You can specify custom version subclasses with the `:class_name` option:
 
@@ -1016,13 +1071,13 @@ end
 
 Unlike ActiveRecord's `class_name`, you'll have to supply the complete module path to the class (e.g. `Foo::BarVersion` if your class is inside the module `Foo`).
 
-### Advantages
+#### Advantages
 
 1. For models which have a lot of versions, storing each model's versions in a
    separate table can improve the performance of certain database queries.
 1. Store different version [metadata](#storing-metadata) for different models.
 
-### Configuration
+#### Configuration
 
 If you are using Postgres, you should also define the sequence that your custom
 version class will use:
@@ -1068,7 +1123,7 @@ class Post < ActiveRecord::Base
 end
 ```
 
-## Custom Serializer
+### 6.b. Custom Serializer
 
 By default, PaperTrail stores your changes as a `YAML` dump. You can override
 this with the serializer config option:
@@ -1083,7 +1138,7 @@ method.  These serializers are included in the gem for your convenience:
 * [PaperTrail::Serializers::YAML][24] - Default
 * [PaperTrail::Serializers::JSON][25]
 
-### PostgreSQL JSON column type support
+#### PostgreSQL JSON column type support
 
 If you use PostgreSQL, and would like to store your `object` (and/or
 `object_changes`) data in a column of [type `json` or type `jsonb`][26], specify
@@ -1101,7 +1156,7 @@ end
 If you use the PostgreSQL `json` or `jsonb` column type, you do not need
 to specify a `PaperTrail.serializer`.
 
-#### Convert existing YAML data to JSON
+##### Convert existing YAML data to JSON
 
 If you've been using PaperTrail for a while with the default YAML serializer
 and you want to switch to JSON or JSONB, you're in a bit of a bind because
@@ -1153,7 +1208,7 @@ remove_column :versions, :old_object
 If you use the optional `object_changes` column, don't forget to convert it
 also, using the same technique.
 
-#### Convert a Column from Text to JSON
+##### Convert a Column from Text to JSON
 
 If your `object` column already contains JSON data, and you want to change its
 data type to `json` or `jsonb`, you can use the following [DDL][36]. Of course,
@@ -1182,12 +1237,12 @@ class ConvertVersionsObjectToJson < ActiveRecord::Migration
 end
 ```
 
-## Testing
+## 7. Testing
 
 You may want to turn PaperTrail off to speed up your tests.  See [Turning
 PaperTrail Off](#turning-papertrail-off) above.
 
-### Minitest
+### 7.a. Minitest
 
 First, disable PT for the entire `ruby` process.
 
@@ -1227,7 +1282,7 @@ test "something that needs versioning" do
 end
 ```
 
-### RSpec
+### 7.b. RSpec
 
 PaperTrail provides a helper, `paper_trail/frameworks/rspec.rb`, that works with
 [RSpec][27] to make it easier to control when `PaperTrail` is enabled during
@@ -1317,7 +1372,7 @@ matcher
 
 ```
 
-### Cucumber
+### 7.c. Cucumber
 
 PaperTrail provides a helper for [Cucumber][28] that works similar to the RSpec
 helper.If you wish to use the helper, you will need to require in your cucumber
@@ -1350,7 +1405,7 @@ test to help prevent data spillover between tests. If you are using PaperTrail
 with Rails, the helper will automatically set the `PaperTrail.controller_info`
 value to `{}` as well, again, to help prevent data spillover between tests.
 
-### Spork
+### 7.d. Spork
 
 If you wish to use the `RSpec` or `Cucumber` helpers with [Spork][29], you will
 need to manually require the helper(s) in your `prefork` block on your test
@@ -1373,7 +1428,7 @@ Spork.prefork do
 end
 ```
 
-### Zeus or Spring
+### 7.e. Zeus or Spring
 
 If you wish to use the `RSpec` or `Cucumber` helpers with [Zeus][30] or
 [Spring][31], you will need to manually require the helper(s) in your test
@@ -1389,25 +1444,9 @@ require 'rspec/rails'
 require 'paper_trail/frameworks/rspec'
 ```
 
-## Testing PaperTrail
-
-Paper Trail has facilities to test against Postgres, Mysql and SQLite. To switch
-between DB engines you will need to export the DB variable for the engine you
-wish to test against.
-
-Though be aware we do not have the ability to create the db's (except sqlite) for
-you. You can look at .travis.yml before_script for an example of how to create
-the db's needed.
-
-```
-export DB=postgres
-export DB=mysql
-export DB=sqlite # this is default
-```
-
-## Sinatra
+## 8. Sinatra
 
-In order to configure PaperTrail for usage with [Sinatra][12], your `Sinatra`
+To configure PaperTrail for usage with [Sinatra][12], your `Sinatra`
 app must be using `ActiveRecord` 3 or 4. It is also recommended to use the
 [Sinatra ActiveRecord Extension][13] or something similar for managing your
 applications `ActiveRecord` connection in a manner similar to the way `Rails`