database_cleaner 1.6.2 → 1.8.5

data/README.markdown

@@ -1,149 +1,76 @@
+<!--
+**If you're viewing this at https://github.com/DatabaseCleaner/database_cleaner,
+you're reading the documentation for the `master` branch.
+[View documentation for the latest release
+(1.7.0).](https://github.com/DatabaseCleaner/database_cleaner/blob/v1.7.0/README.markdown)**
+-->
 # Database Cleaner
 
 [![Build Status](https://travis-ci.org/DatabaseCleaner/database_cleaner.svg?branch=master)](https://travis-ci.org/DatabaseCleaner/database_cleaner)
 [![Code Climate](https://codeclimate.com/github/DatabaseCleaner/database_cleaner/badges/gpa.svg)](https://codeclimate.com/github/DatabaseCleaner/database_cleaner)
+![Gem Version](https://badge.fury.io/rb/database_cleaner.svg)
+[![SemVer](https://api.dependabot.com/badges/compatibility_score?dependency-name=database_cleaner&package-manager=bundler&version-scheme=semver)](https://dependabot.com/compatibility-score.html?dependency-name=database_cleaner&package-manager=bundler&version-scheme=semver)
 
-Database Cleaner is a set of strategies for cleaning your database in Ruby.
+Database Cleaner is a set of gems containing strategies for cleaning your database in Ruby.
 
 The original use case was to ensure a clean state during tests.
 Each strategy is a small amount of code but is code that is usually needed in any ruby app that is testing with a database.
 
 ## Gem Setup
 
+Instead of using the `database_cleaner` gem directly, each ORM has its own gem. Most projects will only need the `database_cleaner-active_record` gem:
+
 ```ruby
 # Gemfile
 group :test do
-  gem 'database_cleaner'
+  gem 'database_cleaner-active_record'
 end
 ```
 
-## Supported Databases, Libraries and Strategies
-
-ActiveRecord, DataMapper, Sequel, MongoMapper, Mongoid, CouchPotato, Ohm and Redis are supported.
-
-Here is an overview of the strategies supported for each library:
-
-<table>
-  <tbody>
-    <tr>
-      <th>ORM</th>
-      <th>Truncation</th>
-      <th>Transaction</th>
-      <th>Deletion</th>
-    </tr>
-    <tr>
-      <td> ActiveRecord </td>
-      <td> Yes</td>
-      <td> <b>Yes</b></td>
-      <td> Yes</td>
-    </tr>
-    <tr>
-      <td> DataMapper</td>
-      <td> Yes</td>
-      <td> <b>Yes</b></td>
-      <td> No</td>
-    </tr>
-    <tr>
-      <td> CouchPotato</td>
-      <td> <b>Yes</b></td>
-      <td> No</td>
-      <td> No</td>
-    </tr>
-    <tr>
-      <td> MongoMapper</td>
-      <td> <b>Yes</b></td>
-      <td> No</td>
-      <td> No</td>
-    </tr>
-    <tr>
-      <td> Mongoid</td>
-      <td> <b>Yes</b></td>
-      <td> No</td>
-      <td> No</td>
-    </tr>
-    <tr>
-      <td> Sequel</td>
-      <td> <b>Yes</b></td>
-      <td> Yes</td>
-      <td> Yes</td>
-    </tr>
-    <tr>
-      <td>Redis</td>
-      <td><b>Yes</b></td>
-      <td>No</td>
-      <td>No</td>
-    </tr>
-    <tr>
-      <td>Ohm</td>
-      <td><b>Yes</b></td>
-      <td>No</td>
-      <td>No</td>
-    </tr>
-    <tr>
-      <td>Neo4j</td>
-      <td>Yes</td>
-      <td>Yes*</td>
-      <td>Yes*</td>
-    </tr>
-  </tbody>
-</table>
-
-\* Truncation and Deletion strategies for Neo4j will just delete all nodes and relationships from the database.
-
-<table>
-  <tbody>
-    <tr>
-      <th>Driver</th>
-      <th>Truncation</th>
-      <th>Transaction</th>
-      <th>Deletion</th>
-    </tr>
-    <tr>
-      <td> Mongo</td>
-      <td> Yes</td>
-      <td> No</td>
-      <td> No</td>
-    </tr>
-    <tr>
-      <td> Moped</td>
-      <td> Yes</td>
-      <td> No</td>
-      <td> No</td>
-    </tr>
-  </tbody>
-</table>
-
-(Default strategy for each library is denoted in bold)
+If you are using multiple ORMs, just load multiple gems:
 
-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).
+```ruby
+# Gemfile
+group :test do
+  gem 'database_cleaner-active_record'
+  gem 'database_cleaner-redis'
+end
+```
 
-## What strategy is fastest?
+## List of adapters
 
-For the SQL libraries the fastest option will be to use `:transaction` as transactions are simply rolled back. If you can use this strategy you should. However, if you wind up needing to use multiple database connections in your tests (i.e. your tests run in a different process than your application) then using this strategy becomes a bit more difficult. You can get around the problem a number of ways.
+Here is an overview of the databases and ORMs supported by each adapter:
 
-One common approach is to force all processes to use the same database connection ([common ActiveRecord hack](http://blog.plataformatec.com.br/2011/12/three-tips-to-improve-the-performance-of-your-test-suite/)) however this approach has been reported to result in non-deterministic failures.
+MySQL, PostgreSQL, SQLite, etc
+* [database_cleaner-active_record](adapters/database_cleaner-active_record)
+* [database_cleaner-sequel](adapters/database_cleaner-sequel)
+* [database_cleaner-data_mapper](adapters/database_cleaner-data_mapper)
 
-Another approach is to have the transactions rolled back in the application's process and relax the isolation level of the database (so the tests can read the uncommitted transactions).
+CouchDB
+* [database_cleaner-couch_potato](adapters/database_cleaner-couch_potato)
 
-An easier, but slower, solution is to use the `:truncation` or `:deletion` strategy.
+MongoDB
+ * [database_cleaner-mongoid](adapters/database_cleaner-mongoid)
+ * [database_cleaner-mongo_mapper](adapters/database_cleaner-mongo_mapper)
+ * [database_cleaner-moped](adapters/database_cleaner-moped)
+ * [database_cleaner-mongo](adapters/database_cleaner-mongo)
 
-So what is fastest out of `:deletion` and `:truncation`? Well, it depends on your table structure and what percentage of tables you populate in an average test. The reasoning is out of the scope of this README but here is a [good SO answer on this topic for Postgres](http://stackoverflow.com/questions/11419536/postgresql-truncation-speed/11423886#11423886).
+Redis
+ * [database_cleaner-redis](adapters/database_cleaner-redis)
+ * [database_cleaner-ohm](adapters/database_cleaner-ohm)
 
-Some people report much faster speeds with `:deletion` while others say `:truncation` is faster for them. The best approach therefore is it try all options on your test suite and see what is faster.
-
-If you are using ActiveRecord then take a look at the [additional options](#additional-activerecord-options-for-truncation) available for `:truncation`.
+Neo4j
+ * [database_cleaner-neo4j](adapters/database_cleaner-neo4j)
 
-## Dependencies
+More details on available configuration options can be found in the README for the specific adapter gem that you're using.
 
-Because database_cleaner supports multiple ORMs, it doesn't make sense to include all the dependencies for each one in the gemspec. However, the DataMapper adapter does depend on dm-transactions. Therefore, if you use DataMapper, you must include dm-transactions in your Gemfile/bundle/gemset manually.
+For support or to discuss development please use the [Google Group](https://groups.google.com/group/database_cleaner).
 
 ## How to use
 
 ```ruby
-require 'database_cleaner'
+require 'database_cleaner/active_record'
 
 DatabaseCleaner.strategy = :truncation
 
@@ -161,15 +88,12 @@ DatabaseCleaner.strategy = :truncation, {:only => %w[widgets dogs some_other_tab
 DatabaseCleaner.strategy = :truncation, {:except => %w[widgets]}
 ```
 
-With Ohm and Redis, `:only` and `:except` take a list of strings to be
-passed to [`keys`](http://redis.io/commands/keys)).
-
 (I should point out the truncation strategy will never truncate your schema_migrations table.)
 
 Some strategies need to be started before tests are run (for example the `:transaction` strategy needs to know to open up a transaction). This can be accomplished by calling `DatabaseCleaner.start` at the beginning of the run, or by running the tests inside a block to `DatabaseCleaner.cleaning`. So you would have:
 
 ```ruby
-require 'database_cleaner'
+require 'database_cleaner/active_record'
 
 DatabaseCleaner.strategy = :transaction
 
@@ -191,7 +115,7 @@ At times you may want to do a single clean with one strategy.
 For example, you may want to start the process by truncating all the tables, but then use the faster transaction strategy the remaining time. To accomplish this you can say:
 
 ```ruby
-require 'database_cleaner'
+require 'database_cleaner/active_record'
 
 DatabaseCleaner.clean_with :truncation
 
@@ -200,17 +124,26 @@ DatabaseCleaner.strategy = :transaction
 # then make the DatabaseCleaner.start and DatabaseCleaner.clean calls appropriately
 ```
 
-### Additional ActiveRecord options for Truncation
+## What strategy is fastest?
 
-The following options are available for ActiveRecord's `:truncation` strategy _only_ for MySQL and Postgres.
+For the SQL libraries the fastest option will be to use `:transaction` as transactions are simply rolled back. If you can use this strategy you should. However, if you wind up needing to use multiple database connections in your tests (i.e. your tests run in a different process than your application) then using this strategy becomes a bit more difficult. You can get around the problem a number of ways.
 
-* `:pre_count` - When set to `true` this will check each table for existing rows before truncating it.  This can speed up test suites when many of the tables to be truncated are never populated. Defaults to `:false`. (Also, see the section on [What strategy is fastest?](#what-strategy-is-fastest))
-* `:reset_ids` - This only matters when `:pre_count` is used, and it will make sure that a tables auto-incrementing id is reset even if there are no rows in the table (e.g. records were created in the test but also removed before DatabaseCleaner gets to it). Defaults to `true`.
+One common approach is to force all processes to use the same database connection ([common ActiveRecord hack](http://blog.plataformatec.com.br/2011/12/three-tips-to-improve-the-performance-of-your-test-suite/)) however this approach has been reported to result in non-deterministic failures.
 
-The following option is available for ActiveRecord's `:truncation` and `:deletion` strategy for any DB.
+Another approach is to have the transactions rolled back in the application's process and relax the isolation level of the database (so the tests can read the uncommitted transactions).
 
-* `:cache_tables` - When set to `true` the list of tables to truncate or delete from will only be read from the DB once, otherwise it will be read before each cleanup run. Set this to `false` if (1) you create and drop tables in your tests, or (2) you change Postgres schemas (`ActiveRecord::Base.connection.schema_search_path`) in your tests (for example, in a multitenancy setup with each tenant in a different Postgres schema). Defaults to `true`.
+An easier, but slower, solution is to use the `:truncation` or `:deletion` strategy.
+
+So what is fastest out of `:deletion` and `:truncation`? Well, it depends on your table structure and what percentage of tables you populate in an average test. The reasoning is out of the scope of this README but here is a [good SO answer on this topic for Postgres](https://stackoverflow.com/questions/11419536/postgresql-truncation-speed/11423886#11423886).
+
+Some people report much faster speeds with `:deletion` while others say `:truncation` is faster for them. The best approach therefore is it try all options on your test suite and see what is faster.
+
+If you are using ActiveRecord then take a look at the [additional options](#additional-activerecord-options-for-truncation) available for `:truncation`.
 
+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`.
+
+## Test Framework Examples
 
 ### RSpec Example
 
@@ -295,7 +228,7 @@ RSpec.configure do |config|
     # with the specs, so continue to use transaction strategy for speed.
     driver_shares_db_connection_with_specs = Capybara.current_driver == :rack_test
 
-    if !driver_shares_db_connection_with_specs
+    unless driver_shares_db_connection_with_specs
       # Driver is probably for an external browser with an app
       # under test that does *not* share a database connection with the
       # specs, so use truncation strategy.
@@ -345,14 +278,9 @@ If you're using Cucumber with Rails, just use the generator that ships with cucu
 Otherwise, to add DatabaseCleaner to your project by hand, create a file `features/support/database_cleaner.rb` that looks like this:
 
 ```ruby
-begin
-  require 'database_cleaner'
-  require 'database_cleaner/cucumber'
+require 'database_cleaner/active_record'
 
-  DatabaseCleaner.strategy = :truncation
-rescue NameError
-  raise "You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it."
-end
+DatabaseCleaner.strategy = :truncation
 
 Around do |scenario, block|
   DatabaseCleaner.cleaning(&block)
@@ -370,11 +298,14 @@ Sometimes you need to use multiple ORMs in your application.
 You can use DatabaseCleaner to clean multiple ORMs, and multiple connections for those ORMs.
 
 ```ruby
-#How to specify particular orms
+require 'database_cleaner/active_record'
+require 'database_cleaner/mongo_mapper'
+
+# How to specify particular orms
 DatabaseCleaner[:active_record].strategy = :transaction
 DatabaseCleaner[:mongo_mapper].strategy = :truncation
 
-#How to specify particular connections
+# How to specify particular connections
 DatabaseCleaner[:active_record, { :connection => :two }]
 
 # You may also pass in the model directly:
@@ -383,68 +314,6 @@ DatabaseCleaner[:active_record, { :model => ModelWithDifferentConnection }]
 
 Usage beyond that remains the same with `DatabaseCleaner.start` calling any setup on the different configured connections, and `DatabaseCleaner.clean` executing afterwards.
 
-### Configuration options
-
-<table>
-  <tbody>
-    <tr>
-      <th>ORM</th>
-      <th>How to access</th>
-      <th>Notes</th>
-    </tr>
-    <tr>
-      <td> Active Record </td>
-      <td> <code>DatabaseCleaner[:active_record]</code></td>
-      <td> Connection specified as <code>:symbol</code> keys, loaded from <code>config/database.yml</code>. You may also pass in the ActiveRecord model under the <code>:model</code> key.</td>
-    </tr>
-    <tr>
-      <td> Data Mapper</td>
-      <td> <code>DatabaseCleaner[:data_mapper]</code></td>
-      <td> Connection specified as <code>:symbol</code> keys, loaded via Datamapper repositories </td>
-    </tr>
-    <tr>
-      <td> Mongo Mapper</td>
-      <td> <code>DatabaseCleaner[:mongo_mapper]</code></td>
-      <td> Multiple connections not yet supported</td>
-    </tr>
-    <tr>
-      <td> Mongoid</td>
-      <td> <code>DatabaseCleaner[:mongoid]</code></td>
-      <td> Multiple databases supported for Mongoid 3. Specify <code>DatabaseCleaner[:mongoid, {:connection =&gt; :db_name}]</code> </td>
-    </tr>
-    <tr>
-      <td> Moped</td>
-      <td> <code>DatabaseCleaner[:moped]</code></td>
-      <td> It is necessary to configure database name with <code>DatabaseCleaner[:moped].db = db_name</code> otherwise name `default` will be used.</td>
-    </tr>
-    <tr>
-      <td> Couch Potato</td>
-      <td> <code>DatabaseCleaner[:couch_potato]</code></td>
-      <td> Multiple connections not yet supported</td>
-    </tr>
-    <tr>
-      <td> Sequel</td>
-      <td> <code>DatabaseCleaner[:sequel]</code></td>
-      <td> Multiple databases supported; specify <code>DatabaseCleaner[:sequel, {:connection =&gt; Sequel.connect(uri)}]</code></td>
-    </tr>
-    <tr>
-      <td>Redis</td>
-      <td><code>DatabaseCleaner[:redis]</code></td>
-      <td>Connection specified as Redis URI</td>
-    </tr>
-    <tr>
-      <td>Ohm</td>
-      <td><code>DatabaseCleaner[:ohm]</code></td>
-      <td>Connection specified as Redis URI</td>
-    </tr>
-    <tr>
-      <td>Neo4j</td>
-      <td><code>DatabaseCleaner[:neo4j]</code></td>
-      <td>Database type and path(URI) <code>DatabaseCleaner[:neo4j, connection: {type: :server_db, path: 'http://localhost:7475'}].</code></td>
-    </tr>
-  </tbody>
-</table>
-
 ## Why?
 
 One of my motivations for writing this library was to have an easy way to turn on what Rails calls "transactional_fixtures" in my non-rails ActiveRecord projects.
@@ -455,15 +324,15 @@ After copying and pasting code to do this several times I decided to package it
 
 #### 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.
+DatabaseCleaner has a deprecated 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:
+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 require the correct adapter gem:
 
 ```ruby
-# How to setup your ORM explicitly
-DatabaseCleaner[:mongoid].strategy = :truncation
+# Gemfile
+gem "database_cleaner-mongoid"
 ```
 
 ### STDERR is being flooded when using Postgres
@@ -485,34 +354,36 @@ test:
   min_messages: WARNING
 </pre>
 
-### Nothing happens in JRuby with Sequel using transactions
+## Safeguards
 
-Due to an inconsistency in JRuby's implementation of Fibers, Sequel gives a different connection to `DatabaseCleaner.start` than is used for tests run between `.start` and `.clean`. This can be worked around by running your tests in a block like `DatabaseCleaner.cleaning { run_my_tests }` instead, which does not use Fibers.
+DatabaseCleaner comes with safeguards against:
 
-### Model fails to load with Neo4j using transactions
+* Running in production (checking for `ENV`, `RACK_ENV`, and `RAILS_ENV`)
+* Running against a remote database (checking for a `DATABASE_URL` that does not include `localhost`, `.local` or `127.0.0.1`)
 
-When you are using [neo4j](https://github.com/neo4jrb/neo4j) gem it creates schema and reads indexes upon loading models. These operations can't be done during a transaction. You have to preload your models before DatabaseCleaner starts a transaction.
+Both safeguards can be disabled separately as follows.
 
-Add to your rails_helper or spec_helper after requiring database_cleaner:
+Using environment variables:
 
-```ruby
-require 'database_cleaner'
-Dir["#{Rails.root}/app/models/**/*.rb"].each do |model|
-  load model
-end
+```
+export DATABASE_CLEANER_ALLOW_PRODUCTION=true
+export DATABASE_CLEANER_ALLOW_REMOTE_DATABASE_URL=true
 ```
 
-## Debugging
+In Ruby:
 
-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.
+```ruby
+DatabaseCleaner.allow_production = true
+DatabaseCleaner.allow_remote_database_url = true
+```
 
-Here's an example of using the `Rails.logger` in `env.rb`:
+In Ruby, a URL whitelist can be specified. When specified, DatabaseCleaner will only allow `DATABASE_URL` to be equal
+to one of the values specified in the url whitelist like so:
 
 ```ruby
-DatabaseCleaner.logger = Rails.logger
+DatabaseCleaner.url_whitelist = ['postgres://postgres@localhost', 'postgres://foo@bar']
 ```
 
-
 ## COPYRIGHT
 
-Copyright (c) 2014 Ben Mabey. See LICENSE for details.
+See [LICENSE](LICENSE) for details.

data/Rakefile

@@ -1,12 +1,12 @@
 require "rubygems"
 require "bundler"
+require "bundler/gem_tasks"
 Bundler.setup
 
 require 'rake'
 require 'rspec/core'
 require 'rspec/core/rake_task'
 RSpec::Core::RakeTask.new(:spec) do |spec|
-  
   spec.pattern = FileList['spec/**/*_spec.rb']
 end
 
@@ -15,15 +15,19 @@ RSpec::Core::RakeTask.new(:rcov) do |spec|
   spec.rcov = true
 end
 
-begin
-  require 'cucumber/rake/task'
-  Cucumber::Rake::Task.new(:features)
-rescue LoadError
-  puts "Cucumber is not available. In order to run features, you must: sudo gem install cucumber"
-end
+require 'cucumber/rake/task'
+Cucumber::Rake::Task.new(:features)
 
-task :default => [:spec, :features]
+desc "Run adapter test suites"
+task :adapters do
+  Dir["adapters/*"].each do |adapter_dir|
+    Dir.chdir adapter_dir do
+      sh "bundle exec rake"
+    end
+  end
+end
 
+task :default => [:spec, :features, :adapters]
 
 desc "Cleans the project of any tmp file that should not be included in the gemspec."
 task :clean do

data/{lib → adapters/database_cleaner-active_record/lib}/database_cleaner/active_record/base.rb

@@ -1,20 +1,29 @@
-require 'database_cleaner/generic/base'
 require 'active_record'
+require 'database_cleaner/generic/base'
 require 'erb'
+require 'yaml'
 
 module DatabaseCleaner
   module ActiveRecord
-
     def self.available_strategies
       %w[truncation transaction deletion]
     end
 
+    def self.default_strategy
+      :transaction
+    end
+
     def self.config_file_location=(path)
       @config_file_location = path
     end
 
     def self.config_file_location
-      @config_file_location ||= "#{DatabaseCleaner.app_root}/config/database.yml"
+      @config_file_location ||= begin
+        # Has DC.app_root been set? Check in this intrusive way to avoid triggering deprecation warnings if it hasn't.
+        app_root = DatabaseCleaner.send(:configuration).instance_variable_get(:@app_root)
+        root = app_root || Dir.pwd
+        "#{root}/config/database.yml"
+      end
     end
 
     module Base
@@ -79,14 +88,14 @@ module DatabaseCleaner
         if ::ActiveRecord::Base.respond_to?(:descendants)
           database_name = connection_hash["database"] || connection_hash[:database]
           models        = ::ActiveRecord::Base.descendants
-          models.detect { |m| m.connection_pool.spec.config[:database] == database_name }
+          models.select(&:connection_pool).detect { |m| m.connection_pool.spec.config[:database] == database_name }
         end
       end
 
       def establish_connection
         ::ActiveRecord::Base.establish_connection(connection_hash)
+        ::ActiveRecord::Base
       end
-
     end
   end
 end

data/{lib → adapters/database_cleaner-active_record/lib}/database_cleaner/active_record/deletion.rb

@@ -1,7 +1,6 @@
-require 'active_record/base'
+require 'active_record'
 require 'active_record/connection_adapters/abstract_adapter'
 require "database_cleaner/generic/truncation"
-require 'database_cleaner/active_record/base'
 require 'database_cleaner/active_record/truncation'
 
 module DatabaseCleaner
@@ -53,28 +52,31 @@ module DatabaseCleaner::ActiveRecord
     end
 
     def tables_with_new_rows(connection)
-      @db_name ||= connection.instance_variable_get('@config')[:database]
-      stats = table_stats_query(connection, @db_name)
+      stats = table_stats_query(connection)
       if stats != ''
-        connection.exec_query(stats).inject([]) {|all, stat| all << stat['table_name'] if stat['exact_row_count'] > 0; all }
+        connection.select_values(stats)
       else
         []
       end
     end
 
-    def table_stats_query(connection, db_name)
-      if @cache_tables && !@table_stats_query.nil?
-        return @table_stats_query
-      else
-        @table_stats_query = connection.select_values(<<-SQL).join(' UNION ')
-               SELECT CONCAT('SELECT \"', table_name, '\" AS table_name, COUNT(*) AS exact_row_count FROM ', table_name)
-               FROM
-               INFORMATION_SCHEMA.TABLES
-               WHERE
-               table_schema = '#{db_name}'
-               AND #{::DatabaseCleaner::ActiveRecord::Base.exclusion_condition('table_name')};
-        SQL
+    def table_stats_query(connection)
+      @table_stats_query ||= build_table_stats_query(connection)
+    ensure
+      @table_stats_query = nil unless @cache_tables
+    end
+
+    def build_table_stats_query(connection)
+      tables = connection.select_values(<<-SQL)
+        SELECT table_name
+        FROM information_schema.tables
+        WHERE table_schema = database()
+        AND #{::DatabaseCleaner::ActiveRecord::Base.exclusion_condition('table_name')};
+      SQL
+      queries = tables.map do |table|
+        "(SELECT #{connection.quote(table)} FROM #{connection.quote_table_name(table)} LIMIT 1)"
       end
+      queries.join(' UNION ALL ')
     end
 
     def information_schema_exists? connection

data/{lib → adapters/database_cleaner-active_record/lib}/database_cleaner/active_record/truncation.rb

@@ -1,10 +1,10 @@
 require 'active_record/base'
-
+require 'database_cleaner/active_record/base'
 require 'active_record/connection_adapters/abstract_adapter'
 
 #Load available connection adapters
 %w(
-  abstract_mysql_adapter postgresql_adapter sqlite3_adapter mysql_adapter mysql2_adapter
+  abstract_mysql_adapter postgresql_adapter sqlite3_adapter mysql_adapter mysql2_adapter oracle_enhanced_adapter
 ).each do |known_adapter|
   begin
     require "active_record/connection_adapters/#{known_adapter}"
@@ -27,7 +27,11 @@ module DatabaseCleaner
 
       def database_cleaner_table_cache
         # the adapters don't do caching (#130) but we make the assumption that the list stays the same in tests
-        @database_cleaner_tables ||= ::ActiveRecord::VERSION::MAJOR >= 5 ? data_sources : tables
+        @database_cleaner_tables ||= database_tables
+      end
+
+      def database_tables
+        ::ActiveRecord::VERSION::MAJOR >= 5 ? data_sources : tables
       end
 
       def truncate_table(table_name)
@@ -63,22 +67,21 @@ module DatabaseCleaner
         select_value("SELECT EXISTS (SELECT 1 FROM #{quote_table_name(table)} LIMIT 1)").to_i
       end
 
-      # Returns a boolean indicating if the given table has an auto-inc number higher than 0.
-      # Note, this is different than an empty table since an table may populated, the index increased,
-      # but then the table is cleaned.  In other words, this function tells us if the given table
-      # was ever inserted into.
-      def has_been_used?(table)
-        if has_rows?(table)
-          true
-        else
-          # Patch for MysqlAdapter with ActiveRecord 3.2.7 later
-          # select_value("SELECT 1") #=> "1"
-          select_value(<<-SQL).to_i > 1 # returns nil if not present
-          SELECT Auto_increment
+      def auto_increment_value(table)
+        select_value(<<-SQL).to_i
+          SELECT auto_increment
           FROM information_schema.tables
-          WHERE table_name='#{table}';
-          SQL
-        end
+          WHERE table_name = '#{table}'
+          AND table_schema = database()
+        SQL
+      end
+
+      # This method tells us if the given table has been inserted into since its
+      # last truncation. Note that the table might have been populated, which
+      # increased the auto-increment counter, but then cleaned again such that
+      # it appears empty now.
+      def has_been_used?(table)
+        has_rows?(table) || auto_increment_value(table) > 1
       end
 
       def has_rows?(table)
@@ -244,7 +247,7 @@ module DatabaseCleaner::ActiveRecord
     private
 
     def tables_to_truncate(connection)
-      tables_in_db = cache_tables? ? connection.database_cleaner_table_cache : connection.tables
+      tables_in_db = cache_tables? ? connection.database_cleaner_table_cache : connection.database_tables
       to_reject = (@tables_to_exclude + connection.database_cleaner_view_cache)
       (@only || tables_in_db).reject do |table|
         if ( m = table.match(/([^.]+)$/) )
@@ -257,7 +260,9 @@ module DatabaseCleaner::ActiveRecord
 
     # overwritten
     def migration_storage_names
-      [::DatabaseCleaner::ActiveRecord::Base.migration_table_name]
+      result = [::DatabaseCleaner::ActiveRecord::Base.migration_table_name]
+      result << ::ActiveRecord::Base.internal_metadata_table_name if ::ActiveRecord::VERSION::MAJOR >= 5
+      result
     end
 
     def cache_tables?