with_advisory_lock 0.0.3 → 0.0.4

data/README.md

@@ -94,6 +94,10 @@ aren't going to be commonly applicable, and they can be a source of
 
 ## Changelog
 
+### 0.0.4
+
+* Moved require into on_load, which should speed loading when AR doesn't have to spin up
+
 ### 0.0.3
 
 * Fought with ActiveRecord 3.0.x and 3.1.x. You don't want them if you use threads—they fail

data/lib/with_advisory_lock.rb

@@ -1,5 +1,4 @@
-require 'with_advisory_lock/concern'
-
 ActiveSupport.on_load :active_record do
+  require 'with_advisory_lock/concern'
   ActiveRecord::Base.send :include, WithAdvisoryLock::Concern
 end

data/lib/with_advisory_lock/version.rb

@@ -1,3 +1,3 @@
 module WithAdvisoryLock
-  VERSION = "0.0.3"
+  VERSION = "0.0.4"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: with_advisory_lock
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
   prerelease: 
 platform: ruby
 authors:
@@ -214,7 +214,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 1855409000394633980
+      hash: -2231625769835238034
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -223,7 +223,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 1855409000394633980
+      hash: -2231625769835238034
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23