transaction_isolation 1.0.2 → 1.0.3

data/.gitignore

@@ -3,4 +3,4 @@
 Gemfile.lock
 pkg/*
 .idea
-
+test/log/*.log

data/README.md

@@ -1,6 +1,8 @@
 # transaction_isolation
 
-Adds support for setting transaction isolation level in ActiveRecord in a database agnostic way.
+Set transaction isolation level in the ActiveRecord in a database agnostic way.
+Works with MySQL, PostgreSQL and SQLite as long as you are using new adapters mysql2, pg or sqlite3.
+Supports all ANSI SQL isolation levels: :serializable, :repeatable_read, :read_committed, :read_uncommitted.
 
 ## Example
 
@@ -18,7 +20,7 @@ Then run:
 
     bundle
 
-__With Rails it works out of the box__.
+__It works out of the box with Ruby on Rails__.
 
 If you have a standalone ActiveRecord-based project you'll need to call:
 
@@ -28,21 +30,23 @@ __after__ connecting to the database. This is because ActiveRecord loads adapter
 
 ## Features
 
- * Setting transaction isolation level (:read_uncommitted, :read_committed, :repeatable_read, :serializable)
+ * Setting transaction isolation level: :serializable, :repeatable_read, :read_committed, :read_uncommitted
  * Auto-reverting to the original isolation level after the block
  * Database agnostic
- * MySQL2, PostgreSQL and SQLite3 database connection adapters supported
+ * MySQL, PostgreSQL and SQLite supported
  * Exception translation. All deadlocks and serialization errors are wrapped in a ActiveRecord::TransactionIsolationConflict exception
  * Use it in your Rails application or a standalone ActiveRecord-based project
 
+## Testimonials
+
+This gem was initially developed for and successfully works in production at [Kontomierz.pl](http://kontomierz.pl) - the finest Polish personal finance app.
+
 ## Real world example
 
 When implementing a table-based job queue you should ensure that only one worker process can pop a particular job from the queue.
 Wrapping your code in a transaction is not enough because by default databases do not isolate transactions to the full extent,
 which leads to occasional phantom reads. It is therefore necessary to manually raise the transaction isolation level.
-The highest level of transaction isolation is called "serializable".
-
-[Read about isolation levels in Wikipedia](http://tinyurl.com/nrqjbb)
+The highest level of transaction isolation is called "serializable" and that's what we need here:
 
     class QueuedJob < ActiveRecord::Base
 
@@ -64,14 +68,19 @@ The highest level of transaction isolation is called "serializable".
             end
           end
         end
+      rescue ActiveRecord::TransactionConflictError => e
+        logger.warn( e.message )
+        retry
       end
 
     end
 
+[Read more about isolation levels in Wikipedia](http://tinyurl.com/nrqjbb)
+
 ## Requirements
 
- * Ruby 1.9
- * ActiveRecord 3.1+
+ * Ruby 1.9.2
+ * ActiveRecord 3.0.11+
 
 ## Running tests
 

data/lib/transaction_isolation/version.rb

@@ -1,3 +1,3 @@
 module TransactionIsolation
-  VERSION = "1.0.2"
+  VERSION = "1.0.3"
 end

data/test/integration/active_record/connection_adapters/any_adapter/translate_exception_test.rb

@@ -34,13 +34,7 @@ class ActiveRecordTest < MiniTest::Unit::TestCase
             translated_exception = ActiveRecord::Base.connection.send( :translate_exception, StandardError.new( message ), message )
             assert_equal( ActiveRecord::TransactionIsolationConflict, translated_exception.class )
           end
-          
-          #  assert_equal( :read_committed, ActiveRecord::Base.connection.current_isolation_level )
-          #end
-          #
-          #if defined?( ActiveRecord::ConnectionAdapters::SQLite3Adapter )
-          #  assert_equal( :serializable, ActiveRecord::Base.connection.current_isolation_level )
-          #end
+
         end
 
       end

data/test/library_setup.rb

@@ -19,4 +19,7 @@ TransactionIsolation::Test::Migrations.run!
 # Load the code that will be tested
 require 'transaction_isolation'
 
+require 'logger'
+ActiveRecord::Base.logger = Logger.new( File.expand_path( "#{File.dirname( __FILE__ )}/log/test.log" ) )
+
 TransactionIsolation.apply_activerecord_patch

data/{transaction-isolation.gemspec → transaction_isolation.gemspec}

@@ -9,7 +9,9 @@ Gem::Specification.new do |s|
   s.email       = ["qertoip@gmail.com"]
   s.homepage    = "https://github.com/qertoip/transaction_isolation"
   s.summary     = %q{Set transaction isolation level in the ActiveRecord in a database agnostic way.}
-  s.description = %q{Set transaction isolation level in the ActiveRecord in a database agnostic way. Works with MySQL2, PostgreSQL and SQLite3 for all ANSI isolation levels: :serializable, :repeatable_read, :read_committed, :read_uncommitted.}
+  s.description = %q{Set transaction isolation level in the ActiveRecord in a database agnostic way.
+Works with MySQL, PostgreSQL and SQLite as long as you are using new adapters mysql2, pg or sqlite3.
+Supports all ANSI SQL isolation levels: :serializable, :repeatable_read, :read_committed, :read_uncommitted.}
   s.required_ruby_version = '>= 1.9.2'
   
   s.files         = `git ls-files`.split("\n")

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: transaction_isolation
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 1.0.3
   prerelease: 
 platform: ruby
 authors:
@@ -9,11 +9,11 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-02-06 00:00:00.000000000 Z
+date: 2012-02-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
-  requirement: &16896100 !ruby/object:Gem::Requirement
+  requirement: &16306400 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -21,10 +21,15 @@ dependencies:
         version: 3.0.11
   type: :runtime
   prerelease: false
-  version_requirements: *16896100
+  version_requirements: *16306400
 description: ! 'Set transaction isolation level in the ActiveRecord in a database
-  agnostic way. Works with MySQL2, PostgreSQL and SQLite3 for all ANSI isolation levels:
-  :serializable, :repeatable_read, :read_committed, :read_uncommitted.'
+  agnostic way.
+
+  Works with MySQL, PostgreSQL and SQLite as long as you are using new adapters mysql2,
+  pg or sqlite3.
+
+  Supports all ANSI SQL isolation levels: :serializable, :repeatable_read, :read_committed,
+  :read_uncommitted.'
 email:
 - qertoip@gmail.com
 executables: []
@@ -61,7 +66,7 @@ files:
 - test/test_helper.rb
 - test/test_runner.rb
 - tests
-- transaction-isolation.gemspec
+- transaction_isolation.gemspec
 homepage: https://github.com/qertoip/transaction_isolation
 licenses: []
 post_install_message: 
@@ -80,9 +85,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
-      segments:
-      - 0
-      hash: 3266208517833567002
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.15