surgical_strike 0.7.4

data/Gemfile.lock

@@ -0,0 +1,163 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    ZenTest (4.3.3)
+    activerecord (2.3.8)
+      activesupport (= 2.3.8)
+    activesupport (2.3.8)
+    addressable (2.2.0)
+    bson (1.0.4)
+    builder (2.1.2)
+    columnize (0.3.1)
+    couch_potato (0.3.0)
+      couchrest (>= 0.24)
+      json
+    couchrest (1.0.1)
+      json (>= 1.4.6)
+      mime-types (>= 1.15)
+      rest-client (>= 1.5.1)
+    cucumber (0.8.5)
+      builder (~> 2.1.2)
+      diff-lcs (~> 1.1.2)
+      gherkin (~> 2.1.4)
+      json_pure (~> 1.4.3)
+      term-ansicolor (~> 1.0.4)
+    data_objects (0.10.2)
+      addressable (~> 2.1)
+    datamapper (1.0.0)
+      dm-aggregates (= 1.0.0)
+      dm-constraints (= 1.0.0)
+      dm-core (= 1.0.0)
+      dm-core (= 1.0.0)
+      dm-migrations (= 1.0.0)
+      dm-serializer (= 1.0.0)
+      dm-timestamps (= 1.0.0)
+      dm-transactions (= 1.0.0)
+      dm-types (= 1.0.0)
+      dm-validations (= 1.0.0)
+    diff-lcs (1.1.2)
+    dm-aggregates (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-constraints (1.0.0)
+      dm-core (~> 1.0.0)
+      dm-migrations (~> 1.0.0)
+    dm-core (1.0.0)
+      addressable (~> 2.1)
+      extlib (~> 0.9.15)
+    dm-do-adapter (1.0.0)
+      data_objects (~> 0.10.1)
+      dm-core (~> 1.0.0)
+    dm-migrations (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-serializer (1.0.0)
+      dm-core (~> 1.0.0)
+      fastercsv (~> 1.5.3)
+      json_pure (~> 1.4.3)
+    dm-sqlite-adapter (1.0.0)
+      dm-do-adapter (~> 1.0.0)
+      do_sqlite3 (~> 0.10.2)
+    dm-timestamps (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-transactions (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-types (1.0.0)
+      dm-core (~> 1.0.0)
+      fastercsv (~> 1.5.3)
+      json_pure (~> 1.4.3)
+      stringex (~> 1.1.0)
+      uuidtools (~> 2.1.1)
+    dm-validations (1.0.0)
+      dm-core (~> 1.0.0)
+    do_sqlite3 (0.10.2)
+      data_objects (= 0.10.2)
+    durran-validatable (2.0.1)
+    extlib (0.9.15)
+    fastercsv (1.5.3)
+    ffi (0.6.3)
+      rake (>= 0.8.7)
+    gemcutter (0.6.1)
+    gherkin (2.1.5)
+      trollop (~> 1.16.2)
+    git (1.2.5)
+    growl (1.0.3)
+    jeweler (1.4.0)
+      gemcutter (>= 0.1.0)
+      git (>= 1.2.5)
+      rubyforge (>= 2.0.0)
+    jnunemaker-validatable (1.8.4)
+      activesupport (>= 2.3.4)
+    json (1.4.6)
+    json_pure (1.4.6)
+    libnotify (0.2.0)
+      ffi (>= 0.6.2)
+    linecache (0.43)
+    mime-types (1.16)
+    mongo (1.0.7)
+      bson (>= 1.0.4)
+    mongo_mapper (0.8.2)
+      activesupport (>= 2.3.4)
+      jnunemaker-validatable (~> 1.8.4)
+      plucky (~> 0.3.1)
+    mongoid (1.9.1)
+      activesupport (<= 3.0.0)
+      bson (~> 1.0.1)
+      durran-validatable (>= 2.0.1)
+      mongo (~> 1.0.1)
+      will_paginate (< 2.9)
+    plucky (0.3.4)
+      mongo (~> 1.0.7)
+    rake (0.8.7)
+    rb-inotify (0.8.1)
+      ffi (>= 0.5.0)
+    rcov (0.9.8)
+    rest-client (1.6.0)
+      mime-types (>= 1.16)
+    rspactor (0.7.0.beta.6)
+      bundler (>= 1.0.0.rc.5)
+      growl (>= 1.0.3)
+      libnotify (>= 0.1.3)
+      rb-inotify
+      sys-uname (>= 0.8.4)
+      trollop (>= 1.16.2)
+    rspec (1.3.0)
+    ruby-debug (0.10.3)
+      columnize (>= 0.1)
+      ruby-debug-base (~> 0.10.3.0)
+    ruby-debug-base (0.10.3)
+      linecache (>= 0.3)
+    rubyforge (2.0.4)
+      json_pure (>= 1.1.7)
+    sequel (3.21.0)
+    sqlite3-ruby (1.3.1)
+    stringex (1.1.0)
+    sys-uname (0.8.4)
+    term-ansicolor (1.0.5)
+    trollop (1.16.2)
+    tzinfo (0.3.22)
+    uuidtools (2.1.1)
+    will_paginate (2.3.14)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  ZenTest
+  activerecord (= 2.3.8)
+  bundler
+  couch_potato (= 0.3.0)
+  cucumber
+  datamapper (= 1.0.0)
+  dm-migrations (= 1.0.0)
+  dm-sqlite-adapter (= 1.0.0)
+  jeweler
+  json_pure
+  mongo_mapper (= 0.8.2)
+  mongoid (= 1.9.1)
+  rake
+  rcov
+  rspactor
+  rspec
+  ruby-debug
+  sequel (~> 3.21.0)
+  sqlite3-ruby
+  tzinfo (= 0.3.22)

data/History.txt

@@ -0,0 +1,210 @@
+== 0.7.x (in git)
+
+== 0.7.2 2012-03-21
+
+  * Proper Mysql2Adapter superclass fix. (Jonathan Viney)
+  * Sequel::Transaction works with latest Sequel. (David Barri)
+  * Postgres Adapter no longer generates invalid SQL when no tables provided. (Michael-Keith Bernard)
+  * Documenation fixes/improvements. (David Barri, Ben Mabey, Kevin Moore)
+
+== 0.7.1 2012-01-15
+
+ === New Features
+
+ * Support for Rails 3.2. (David Demaree)
+
+=== Bugfixes
+
+  * Truncation resets the id count on SQLite. (Jordan Hollinger)
+  * AR delete strategy now disables referential integrity. (Ben Mabey)
+  * Fixes Postgres adapter for JRuby. (Dmytrii Nagirniak, Uģis Ozols)
+  * Documenation fixes. (Josh Rendek, Joshua Flanagan)
+  * Fixes bad error message when no database is specified for AR. (issue #72, Ben Mabey)
+
+
+== 0.7.0 2011-11-12
+
+ === New Features
+
+ * Sequel Support (Corin Langosch)
+ * Updates DataMapper strategies to work with DataMapper 1.1 (Xavier Shay and Anthony Williams)
+ * for AR and PSQL, truncate all tables with one command, improving performance due to avoiding cascades (Leonid Shevtsov)
+
+=== Bugfixes
+
+  * Avoids trying to load the ':default' ActiveRecord config. #72 (Ben Mabey)
+
+
+== 0.6.7 2011-04-21
+
+=== Bugfixes
+ * Explicity require ERB. (Vít Ondruch)
+ * Cache DB connections, fixes referential integrity bug when using multiple DBs. (John Ferlito)
+
+== 0.6.6 2011-03-16
+
+=== Bugfixes
+ * Don't modify the array passed in with the :except key. (Eric Wollesen)
+ * Fixes version checking for postgresql. (Greg Barnett)
+
+== 0.6.5 2011-03-08
+
+=== Bugfixes
+ * When truncating in postgresql (>= 8.4) sequences are now reset. (Greg Barnett)
+ * Fixes the MongoDB truncation so non system collections starting with 'system' are not excluded for truncation. (Dmitry Naumov)
+
+== 0.6.4 2011-02-21
+
+=== Bugfixes
+ * Avoids trying to drop views in Postgres. (Bernerd Schaefer)
+
+== 0.6.3 2011-02-09
+
+ === New Features
+  * Configurable logger to aid in debugging database cleaner. (Marty Haught)
+
+== 0.6.2 2011-02-04
+
+ === New Features
+  * Support IBM_DB Adapter for table truncation. This is for DB2 >= 9.7 (GH-39 Samer Abukhait)
+
+ === Bugfixes
+  * Reversed GH-41 after larger community discussion. Mongo indexes are no longer dropped. (Ben Mabey)
+  * Truncation strategy works on SqlServer tables with FKs. (GH-33, Hugo Freire)
+
+== 0.6.1 2011-01-27
+
+ === New Features
+  * Default strategies for all ORM libs are defined. (GH-36, GH-38 Prem Sichanugrist)
+  * Add a NullStrategy. (GH-6 Ben Mabey)
+
+ === Bugfixes
+  * Mongo colletion indexes are dropped for collections being removed. (GH-41 Ben Mabey)
+  * Exclude database views from tables_to_truncate, if the connection adapter
+    supports reading from the ANSI standard information_schema views. (GH-25 Samer Abukhait)
+  * ORM types can be specified in string format and not mysteriously blowup. (GH-26 Ben Mabey)
+  * Do not remove MongoDB reserved system collections. (GH-24 Ches Martin)
+
+== 0.6.0 2010-10-25 - The Multi-ORM/Connection Release
+
+This release has the often asked for functionality of being able to clean
+multiple databases within the same project.  This involves being able to
+clean databases managed by the same ORM (i.e. different connections) and
+also being able to clean databases managed by distinct ORMs.  So, for
+example you can now use DatabaseCleaner on a project that has ActiveRecord
+and Mongoid to help ensure all DBs all in a clean state.  Please see the
+README for more information.  The old API has been preserved so this release
+is backwards compatible.
+
+This release is a result of Jon Rowe's hard work. Many thanks to Jon for all
+of the hours and effort he put into making this feature request a reality.
+
+ === New Features
+  * Ability to clean multiple database connections managed by the same ORM. (Jon Rowe)
+  * Ability to clean multiple DBs managed by different ORMs in same project. (Jon Rowe)
+  * Allows for the ActiveRecord config file (database.yml) to contain ERB and process it. (Fletcher Nichol)
+  * Mysql2Adapter support. (Kamal Fariz Mahyuddin and John Ferlito)
+  * Deletion strategy for ActiveRecord (Mikl Kurkov)
+
+ === Bugfixes
+  * Updates the DataMapper truncation strategy to version 0.10.3. (Robert Rouse)
+  * Addresses Ruby 1.9 and 1.8 differences causing a bug in the AR PostgreSQLAdapter truncation strategy. (GH-14, James B. Byrne)
+  * Fixes syntax error that MySQL was throwing during DataMapper truncation. (Blake Gentry)
+  * Fixes truncation for PostgreSQL (Bodaniel Jeanes and Gabriel Sobrinho)
+  * Workaround for superclass mismatches for the ActiveRecord-jdbc-adapter (Toms Mikoss)
+
+== 0.5.2
+
+ === Bugfixes
+  * Removes extraneous puts call from configuration.rb.  (Ben Mabey)
+
+== 0.5.1 - The Mongoid Release
+
+This release also attempts to fix AR for Rails 3 support.  I have seen mixed reviews on this.  Some people
+claim the fixes allow for use in Rails3 while others have not had good luck with it.  I plan on reworking
+the way AR support is added so that it is more friendly with how Rails 3 uses autoload.
+
+ === New features
+  * Clean and clean_with methods are now aliased to clean! and clean_with!. (Ben Mabey)
+  * Mongoid Support! (Sidney Burks)
+
+=== Bugfixes
+  * Check PostgreSQL version >= 8.2 before using TRUNCATE CASCADE (James B. Byrne)
+  * Correct superclass is used in ActiveRecord connection adapters. (johnathan, Aslak Hellesoy, Ben Mabey)
+
+== 0.5.0 2010-02-22 - The CouchPotato Release
+
+ === New features
+  * Basic truncation support for CouchPotato / CouchDB. (Martin Rehfeld)
+  * SQLite3 on JRuby will fall back to delete if truncate doesn't work. (Darrin Holst)
+  * JDBC is used for ActiveRecord automaticaly when JRuby is detected. (Darrin Holst)
+
+ === Bufixes
+  * MongoMapper truncation strategy now works with :only and :except options. (Ben Mabey)
+
+== 0.4.3 2010-01-17
+
+ === New features
+  * Truncation for ActiveRecord oracle_enhanced adapter. (Edgars Beigarts)
+
+== 0.4.2 2010-01-12
+
+ === Bufixes
+  * Datamapper truncation now uses 'select' instead of deprecated the 'query' method. (Steve Tooke)
+
+== 0.4.1 2010-01-07
+
+ === Bufixes
+  * Postgres tables with FKs now truncate (added TRUNCADE CASCADE) using Datamapper. (Ben Mabey)
+
+== 0.4.0 2009-12-23 (The MongoMapper Edition)
+
+ === New features
+  * MongoMapper support for the truncation strategy. (Aubrey Holland)
+
+== 0.3.0 2009-12-20
+
+ === New features
+  * DataMapper 0.10.0 Compatible. (Martin Gamsjaeger)
+ === Bufixes
+  * Postgres tables with FKs now truncate (added TRUNCADE CASCADE). (Vika - yozhyk on github)
+
+== 0.2.3 2009-05-30
+
+ === New features
+  * Support for SQL Server truncation (Adam Meehan)
+
+== 0.2.2 2009-05-08
+ === Bufixes
+  * Added proper gemspec description and summary. (Ben Mabey, thanks to Martin Gamsjaeger)
+
+ === New features
+
+== 0.2.1 2009-05-08
+ === Bufixes
+  * Removed extraneous TruncationBase class definition. (Ben Mabey)
+
+== 0.2.0 2009-05-08 - The Datamapper Release
+
+ === New features
+  * DataMapper strategies (Martin Gamsjaeger)
+    * Transaction
+    * Truncation - working SQLite3, MySQL adapters. Experimental Postgres adapter (not tested).
+
+== 0.1.3 2009-04-30
+
+ === New features
+  * PostgresSQLAdapter for AR to support the truncation strategy. (Alberto Perdomo)
+ === Bufixes
+  * Added missing quotes around table names in truncation calls. (Michael MacDonald)
+
+== 0.1.2 2009-03-05
+ === New features
+  * JDBC Adapter to enable AR truncation strategy to work. (Kamal Fariz Mahyuddin)
+
+== 0.1.1 2009-03-04 - Initial Release (Ben Mabey)
+  * Basic infrastructure
+  * Features, RSpec code examples
+  * ActiveRecord strategies
+    * Truncation - with MySQL, and SQLite3 adapters.
+    * Transaction - wrap your modifications and roll them back.

data/LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2009 Ben Mabey
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.textile

@@ -0,0 +1,229 @@
+h1. Database Cleaner
+
+Database Cleaner is a set of 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.
+
+ActiveRecord, DataMapper, Sequel, MongoMapper, Mongoid, and CouchPotato are supported.
+
+Here is an overview of the strategies supported for each library:
+
+|_. ORM        |_.  Truncation  |_.  Transaction  |_.  Deletion    |
+| ActiveRecord | Yes            | **Yes**         | Yes            |
+| 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)
+
+The ActiveRecord @:deletion@ strategy is useful for when the @:truncation@ strategy causes
+locks (as reported by some Oracle DB users).  The @:deletion@ option has been reported to
+be faster than @:truncation@ in some cases as well.  In general, the best approach is to use
+@:transaction@ since it is the fastest.
+
+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. Dependencies
+
+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.  
+
+h2. How to use
+
+<pre>
+  require 'database_cleaner'
+  DatabaseCleaner.strategy = :truncation
+
+  # then, whenever you need to clean the DB
+  DatabaseCleaner.clean
+</pre>
+
+With the :truncation strategy you can also pass in options, for example:
+<pre>
+  DatabaseCleaner.strategy = :truncation, {:only => %w[widgets dogs some_other_table]}
+</pre>
+
+<pre>
+  DatabaseCleaner.strategy = :truncation, {:except => %w[widgets]}
+</pre>
+
+(I should point out the truncation strategy will never truncate your schema_migrations table.)
+
+Some strategies require that you call DatabaseCleaner.start before calling clean
+(for example the :transaction one needs to know to open up a transaction). So
+you would have:
+
+<pre>
+  require 'database_cleaner'
+  DatabaseCleaner.strategy = :transaction
+
+  DatabaseCleaner.start # usually this is called in setup of a test
+  dirty_the_db
+  DatabaseCleaner.clean # cleanup of the test
+</pre>
+
+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:
+
+<pre>
+  require 'database_cleaner'
+  DatabaseCleaner.clean_with :truncation
+  DatabaseCleaner.strategy = :transaction
+  # then make the DatabaseCleaner.start and DatabaseCleaner.clean calls appropriately
+</pre>
+
+h3. RSpec Example
+
+<pre>
+RSpec.configure do |config|
+
+  config.before(:suite) do
+    DatabaseCleaner.strategy = :transaction
+    DatabaseCleaner.clean_with(:truncation)
+  end
+
+  config.before(:each) do
+    DatabaseCleaner.start
+  end
+
+  config.after(:each) do
+    DatabaseCleaner.clean
+  end
+
+end
+</pre>
+
+h3. Cucumber Example
+
+Add this to your features/support/env.rb file:
+
+<pre>
+begin
+  require 'database_cleaner'
+  require 'database_cleaner/cucumber'
+  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
+</pre>
+
+A good idea is to create the before and after hooks to use the DatabaseCleaner.start and DatabaseCleaner.clean methods.
+
+Inside features/support/hooks.rb:
+
+<pre>
+Before do
+  DatabaseCleaner.start
+end
+
+After do |scenario|
+  DatabaseCleaner.clean
+end
+</pre>
+
+This should cover the basics of tear down between scenarios and keeping your database clean.
+For more examples see the section "Why?"
+
+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.
+
+<pre>
+  #How to specify particular orms
+  DatabaseCleaner[:active_record].strategy = :transaction
+  DatabaseCleaner[:mongo_mapper].strategy = :truncation
+
+  #How to specify particular connections
+  DatabaseCleaner[:active_record,{:connection => :two}]
+</pre>
+
+Usage beyond that remains the same with DatabaseCleaner.start calling any setup on the different configured connections, and DatabaseCleaner.clean executing afterwards.
+
+Configuration options
+
+
+|_. ORM         |_.   How to access               |_.   Notes                                                                |
+| Active Record | DatabaseCleaner[:active_record] | Connection specified as :symbol keys, loaded from config/database.yml    |
+| Data Mapper   | DatabaseCleaner[:data_mapper]   | Connection specified as :symbol keys, loaded via Datamapper repositories |
+| Mongo Mapper  | DatabaseCleaner[:mongo_mapper]  | Multiple connections not yet supported                                   |
+| Mongoid       | DatabaseCleaner[:mongoid]       | Multiple connections not yet supported                                   |
+| Couch Potato  | DatabaseCleaner[:couch_potato]  | Multiple connections not yet supported                                   |
+| Sequel        | DatabaseCleaner[:sequel]        | ?                                                                        |
+
+h2. 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.  For example, Cucumber ships with a Rails world that
+will wrap each scenario in a transaction.  This is great, but what if you are
+using ActiveRecord in a non-rails project?  You used to have to copy-and-paste
+the needed code, but with DatabaseCleaner you can now say:
+
+<pre>
+  #env.rb
+  require 'database_cleaner'
+  require 'database_cleaner/cucumber'
+  DatabaseCleaner.strategy = :transaction
+</pre>
+
+Now lets say you are running your features and it requires that another process be
+involved (i.e. Selenium running against your app's server.)  You can simply change
+your strategy type:
+
+<pre>
+  #env.rb
+  require 'database_cleaner'
+  require 'database_cleaner/cucumber'
+  DatabaseCleaner.strategy = :truncation
+</pre>
+
+You can have the best of both worlds and use the best one for the job:
+<pre>
+  #env.rb
+  require 'database_cleaner'
+  require 'database_cleaner/cucumber'
+  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/TODO

@@ -0,0 +1,3 @@
+Could be more Datamapper
+MongoMapper multiple db support
+CouchDB multiple db support

data/VERSION.yml

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

data/cucumber.yml

@@ -0,0 +1 @@
+default: features

data/examples/Gemfile

@@ -0,0 +1 @@
+../Gemfile

data/examples/Gemfile.lock

@@ -0,0 +1 @@
+../Gemfile.lock

data/examples/config/database.yml.example

@@ -0,0 +1,8 @@
+#This is an example of what database.yml *should* look like (when I wrote it)
+#The real database.yml is generated automatically by the active record model lib (so it can be correct)
+two: 
+  adapter: sqlite3
+  database: /path/to/examples/features/support/../../db/activerecord_two.db
+one: 
+  adapter: sqlite3
+  database: /path/to/examples/features/support/../../db/activerecord_one.db

data/examples/features/example.feature

@@ -0,0 +1,11 @@
+Feature: example
+ In order to test DataBase Cleaner
+ Here are some scenarios that rely on the DB being clean!
+
+  Scenario: dirty the db
+    When I create a widget
+    Then I should see 1 widget
+
+  Scenario: assume a clean db
+    When I create a widget
+    Then I should see 1 widget

data/examples/features/example_multiple_db.feature

@@ -0,0 +1,23 @@
+Feature: example
+ In order to test DataBase Cleaner
+ Here are some scenarios that rely on the DB being clean!
+
+  # Background:
+  #   Given I have setup DatabaseCleaner to clean multiple databases
+  #
+  Scenario: dirty the db
+    When I create a widget in one db
+     And I create a widget in another db
+    Then I should see 1 widget in one db
+     And I should see 1 widget in another db
+
+  Scenario: assume a clean db
+    When I create a widget in one db
+    Then I should see 1 widget in one db
+     And I should see 0 widget in another db
+
+  Scenario: assume a clean db
+    When I create a widget in another db
+    Then I should see 0 widget in one db
+     And I should see 1 widget in another db
+