database_cleaner 0.7.1 → 0.7.2

data/History.txt

@@ -1,5 +1,11 @@
 == 0.7.x (in git)
 
+== 0.7.2 2012-03-21
+
+  * Proper Mysql2Adapter fix (Jonathan Viney)
+  * Sequel::Transaction works with latest Sequel (David Barri)
+  * Documenation fixes/improvements (David Barri, Ben Mabey, Kevin Moore)
+
 == 0.7.1 2012-01-15
 
  === New Features

data/README.textile

@@ -14,6 +14,7 @@ Here is an overview of the strategies supported for each library:
 | DataMapper   | Yes            | **Yes**         | No             |
 | CouchPotato  | **Yes**        | No              | No             |
 | MongoMapper  | **Yes**        | No              | No             |
+| Mongoid      | **Yes**        | No              | No             |
 | Sequel       | **Yes**        | Yes             | No             |
 
 (Default strategy for each library is denoted in bold)
@@ -26,6 +27,8 @@ be faster than @:truncation@ in some cases as well.  In general, the best approa
 Database Cleaner also includes a @null@ strategy (that does no cleaning at all) which can be used
 with any ORM library. You can also explicitly use it by setting your strategy to @nil@.
 
+For support or to discuss development please use the "Google Group":http://groups.google.com/group/database_cleaner.
+
 h2. How to use
 
 <pre>
@@ -123,21 +126,6 @@ end
 This should cover the basics of tear down between scenarios and keeping your database clean.
 For more examples see the section "Why?"
 
-h2. Common Errors
-
-In rare cases DatabaseCleaner will encounter errors that it will log.  By default it uses STDOUT set to the ERROR level but you can configure this to use whatever Logger you desire.  Here's an example of using the Rails.logger in env.rb:
-
-<pre>
-  DatabaseCleaner.logger = Rails.logger
-</pre>
-
-If you are using Postgres and have foreign key constraints, the truncation strategy will cause a lot of extra noise to appear on STDERR (in
-the form of "NOTICE truncate cascades" messages). To silence these warnings set the following log level in your postgresql.conf file:
-
-<pre>
-  client_min_messages = warning
-</pre>
-
 h2. How to use with multiple ORM's
 
 Sometimes you need to use multiple ORMs in your application. You can use DatabaseCleaner to clean multiple ORMs, and multiple connections for those ORMs.
@@ -199,6 +187,37 @@ You can have the best of both worlds and use the best one for the job:
   DatabaseCleaner.strategy = (ENV['SELENIUM'] == 'true') ? :truncation : :transaction
 </pre>
 
+
+h2. Common Errors
+
+h4. DatabaseCleaner is trying to use the wrong ORM
+
+DatabaseCleaner has an autodetect mechanism where if you do not explicitly define your ORM it will use the first ORM it can detect that is loaded.  Since ActiveRecord is the most common ORM used that is the first one checked for.  Sometimes other libraries (e.g. ActiveAdmin) will load other ORMs (e.g. ActiveRecord) even though you are using a different ORM.  This will result in DatabaseCleaner trying to use the wrong ORM (e.g. ActiveRecord) unless you explicitly define your ORM like so:
+
+<pre>
+  # How to setup your ORM explicitly
+  DatabaseCleaner[:mongoid].strategy = :truncation
+</pre>
+
+h4. STDERR is being flooded when using Postgres
+
+If you are using Postgres and have foreign key constraints, the truncation strategy will cause a lot of extra noise to appear on STDERR (in
+the form of "NOTICE truncate cascades" messages). To silence these warnings set the following log level in your postgresql.conf file:
+
+<pre>
+  client_min_messages = warning
+</pre>
+
+
+h2. Debugging
+
+In rare cases DatabaseCleaner will encounter errors that it will log.  By default it uses STDOUT set to the ERROR level but you can configure this to use whatever Logger you desire.  Here's an example of using the Rails.logger in env.rb:
+
+<pre>
+  DatabaseCleaner.logger = Rails.logger
+</pre>
+
+
 h2. COPYRIGHT
 
 Copyright (c) 2009 Ben Mabey. See LICENSE for details.

data/VERSION.yml

@@ -2,4 +2,4 @@
 :major: 0
 :build: 
 :minor: 7
-:patch: 1
+:patch: 2

data/lib/database_cleaner/active_record/deletion.rb

@@ -15,7 +15,7 @@ module ActiveRecord
       end
     end
 
-    class Mysql2Adapter < AbstractAdapter
+    class Mysql2Adapter < MYSQL2_ADAPTER_PARENT
       def delete_table(table_name)
         execute("DELETE FROM #{quote_table_name(table_name)};")
       end

data/lib/database_cleaner/sequel/transaction.rb

@@ -5,15 +5,20 @@ module DatabaseCleaner
       include ::DatabaseCleaner::Sequel::Base
 
       def start
-        @transactions ||= []
-        db.send(:add_transaction)
-        @transactions << db.send(:begin_transaction, db)
+        @fibers||= []
+        db= self.db
+        f= Fiber.new do
+          db.transaction(:rollback => :always, :savepoint => true) do
+            Fiber.yield
+          end
+        end
+        f.resume
+        @fibers<< f
       end
-  
+
       def clean
-        transaction = @transactions.pop
-        db.send(:rollback_transaction, transaction)
-        db.send(:remove_transaction, transaction)
+        f= @fibers.pop
+        f.resume
       end
     end
   end

data/lib/database_cleaner/sequel/truncation.rb

@@ -8,8 +8,21 @@ module DatabaseCleaner
       include ::DatabaseCleaner::Generic::Truncation
   
       def clean
-        each_table do |db, table|
-          db[table].truncate
+        case db_type= db.url.sub(/:.+/,'').to_sym
+        when :postgres
+          # PostgreSQL requires all tables with FKs to be truncates in the same command, or have the CASCADE keyword
+          # appended. Bulk truncation without CASCADE is:
+          # * Safer. Tables outside of tables_to_truncate won't be affected.
+          # * Faster. Less roundtrips to the db.
+          unless (tables= tables_to_truncate(db)).empty?
+            all_tables= tables.map{|t| %["#{t}"]}.join ','
+            db.run "TRUNCATE TABLE #{all_tables};"
+          end
+        else
+          # Truncate each table normally
+          each_table do |db, table|
+            db[table].truncate
+          end
         end
       end
   
@@ -24,6 +37,12 @@ module DatabaseCleaner
       def tables_to_truncate(db)
         (@only || db.tables) - @tables_to_exclude
       end
+
+      # overwritten
+      def migration_storage_name
+        :schema_info
+      end
+
     end
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: database_cleaner
 version: !ruby/object:Gem::Version 
-  hash: 1
+  hash: 7
   prerelease: 
   segments: 
   - 0
   - 7
-  - 1
-  version: 0.7.1
+  - 2
+  version: 0.7.2
 platform: ruby
 authors: 
 - Ben Mabey
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2012-01-15 00:00:00 Z
+date: 2012-03-21 00:00:00 Z
 dependencies: []
 
 description: Strategies for cleaning databases.  Can be used to ensure a clean state for testing.