hairtrigger 0.2.17 → 0.2.18

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a9ff019936d101e9c5493c4bdecd2d0791382144
-  data.tar.gz: fb958cd57f2e1ee9042d4cedc966974514f446ac
+  metadata.gz: 3c525b3a5e80e73dfe8dfa9d1b6e8cd3f0c9636b
+  data.tar.gz: 4d02307f955177263f83b9412221e3fa2bcab7da
 SHA512:
-  metadata.gz: ce30e5aecef79de39e998c07d7d23c4639fb035d5dacf424f8a984e39dbf9f71dfc89aa789d21bdbf935eca7d72ee6b9d46158d5d7a94bb93f3cb3ede98bff3d
-  data.tar.gz: b65f3cd26a71adc564eec7f5c4baf04b80da610cf6c6d96de817265def64b22e78ba16f4ee31a1bb7604bc2ac4f47fdbf9c3353a71e77085c09882b9a5dfca6f
+  metadata.gz: 5631a904515f61388c15cdd07dad116796f9dd731a8e20e077251ef9c3432351ae82ee34d4ac8c7dfdbe850f1ef17626393796846dc7033ac8c754f83f392cc6
+  data.tar.gz: a90b316838dee6303756ded7833f21905f716699633aba8c50f8769af2f84b3d1fee286870fd8d3f116f7dd043ed64fcb797d3199d2df7de3ab3b6cad4987c9f

data/README.md

@@ -1,5 +1,5 @@
 # HairTrigger
-[<img src="https://secure.travis-ci.org/jenseng/hair_trigger.png?branch=master" />](http://travis-ci.org/jenseng/hair_trigger)
+[<img src="https://secure.travis-ci.org/jenseng/hair_trigger.svg?branch=master" />](http://travis-ci.org/jenseng/hair_trigger)
 
 HairTrigger lets you create and manage database triggers in a concise,
 db-agnostic, Rails-y way. You declare triggers right in your models in Ruby,
@@ -106,7 +106,7 @@ Example: `trigger.after(:update).nowrap { "tsvector_update_trigger(...)" }`
 
 #### declare
 PostgreSQL-specific option for declaring variables for use in the
-trigger function. Declarations should be separate by semicolons, e.g.
+trigger function. Declarations should be separated by semicolons, e.g.
 
 ```ruby
 trigger.after(:insert).declare("user_type text; status text") do
@@ -197,22 +197,22 @@ rolling back.
 
 #### Manual triggers and :compatibility
 
-As bugs are fixed and features are implemented in hairtrigger, it's possible
+As bugs are fixed and features are implemented in HairTrigger, it's possible
 that the generated trigger SQL will change (this has only happened once so
-far). If you upgrade to a newer version of hairtrigger, it needs a way of
+far). If you upgrade to a newer version of HairTrigger, it needs a way of
 knowing which previous version generated the original trigger. You only need
 to worry about this for manual trigger migrations, as the model ones
 automatically take care of this. For your manual triggers you can either:
 
 * pass `:compatibility => x` to your `create_trigger` statement, where x is
-  whatever HairTrigger::Builder.compatiblity is (1 for this version).
+  whatever HairTrigger::Builder.compatibility is (1 for this version).
 * set `HairTrigger::Builder.base_compatibility = x` in an initializer, where
-  x is whatever HairTrigger::Builder.compatiblity is. This is like doing the
+  x is whatever HairTrigger::Builder.compatibility is. This is like doing the
   first option on every `create_trigger`. Note that once the compatibility
   changes, you'll need to set `:compatibility` on new triggers (unless you
   just redo all your triggers and bump the `base_compatibility`).
 
-If you upgrade to a newer version of hairtrigger and see that the SQL
+If you upgrade to a newer version of HairTrigger and see that the SQL
 compatibility has changed, you'll need to set the appropriate compatibility
 on any new triggers that you create.
 
@@ -231,7 +231,7 @@ make it trigger-aware. A newly generated schema.rb will contain:
 As long as you don't delete old migrations and schema.rb prior to running
 `rake db:schema:dump`, the result should be what you expect (and portable).
 If you have deleted all trigger migrations, you can regenerate a new
-baseline for model triggers via rake db:generate_trigger_migration.
+baseline for model triggers via `rake db:generate_trigger_migration`.
 
 ## Testing
 
@@ -262,7 +262,7 @@ when you attempt to run the migration.
 
 Generation warnings are similar but they don't stop the trigger from being
 generated. If you do something adapter-specific supported by your database,
-you will still get a warning ($stderr) that your trigger is not portable. You
+you will still get a warning (to $stderr) that your trigger is not portable. You
 can silence warnings via `HairTrigger::Builder.show_warnings = false`
 
 You can validate your triggers beforehand using the `Builder#validate!` method.
@@ -294,7 +294,7 @@ existing trigger if you wish to redefine it.
 
 ## Gotchas
 
-* As is the case with ActiveRecord::Base.update_all or any direct SQL you do,
+* As is the case with `ActiveRecord::Base.update_all` or any direct SQL you do,
   be careful to reload updated objects from the database. For example, the
   following code will display the wrong count since we aren't reloading the
   account:

data/lib/hair_trigger/version.rb

@@ -1,5 +1,5 @@
 module HairTrigger
-  VERSION = "0.2.17"
+  VERSION = "0.2.18"
 
   def VERSION.<=>(other)
     split(/\./).map(&:to_i) <=> other.split(/\./).map(&:to_i)

data/spec/adapter_spec.rb

@@ -48,12 +48,12 @@ describe "adapter" do
     context "mysql" do
       let(:adapter) { :mysql }
       it_behaves_like "mysql"
-    end
+    end if ADAPTERS.include? :mysql
 
     context "mysql2" do
       let(:adapter) { :mysql2 }
       it_behaves_like "mysql"
-    end
+    end if ADAPTERS.include? :mysql2
 
     context "postgresql" do
       let(:adapter) { :postgresql }

data/spec/spec_helper.rb

@@ -5,11 +5,13 @@ require 'hair_trigger'
 require 'yaml'
 
 CONFIGS = YAML.load_file(File.expand_path(File.dirname(__FILE__) + '/../database.yml'))[ENV["DB_CONFIG"] || "test"]
-ADAPTERS = [:mysql, :mysql2, :postgresql, :sqlite3]
+ADAPTERS = [:mysql2, :postgresql, :sqlite3]
+ADAPTERS.unshift :mysql if ActiveRecord::VERSION::STRING < "5"
 
 def each_adapter
   require 'active_record/connection_adapters/postgresql_adapter'
-  require 'active_record/connection_adapters/mysql_adapter'
+  require 'active_record/connection_adapters/mysql_adapter' if ADAPTERS.include? :mysql
+  require 'active_record/connection_adapters/mysql2_adapter'
   require 'active_record/connection_adapters/sqlite3_adapter'
   require 'mysql2'
 
@@ -54,7 +56,7 @@ shared_context "hairtrigger utils" do
     end
     # Arel has an issue in that it keeps using original connection for quoting,
     # etc. (which breaks stuff) unless you do this:
-    Arel::Visitors::ENGINE_VISITORS.delete(ActiveRecord::Base) if defined?(Arel)
+    Arel::Visitors::ENGINE_VISITORS.delete(ActiveRecord::Base) if defined?(Arel::Visitors::ENGINE_VISITORS)
     ActiveRecord::Base.establish_connection(config)
     ActiveRecord::Base.logger = Logger.new('/dev/null')
     ActiveRecord::SchemaDumper.previous_schema = nil

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: hairtrigger
 version: !ruby/object:Gem::Version
-  version: 0.2.17
+  version: 0.2.18
 platform: ruby
 authors:
 - Jon Jensen
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-12-16 00:00:00.000000000 Z
+date: 2017-02-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -30,28 +30,28 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.7'
+        version: '3.8'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.7'
+        version: '3.8'
 - !ruby/object:Gem::Dependency
   name: ruby2ruby
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.0'
+        version: '2.3'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.0'
+        version: '2.3'
 description: allows you to declare database triggers in ruby in your models, and then
   generate appropriate migrations as they change
 email: jenseng@gmail.com
@@ -106,9 +106,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: 1.3.5
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.5
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: easy database triggers for active record
 test_files: []
-has_rdoc: