git_friendly_dumper 0.0.1

data/features/load/db_dump_path_load.feature

@@ -0,0 +1,63 @@
+Feature: populate database with data and stucture in a custom directory
+  In order to load data found elsewhere than db/dump
+  I want the rake task to use the DUMP_PATH env variable to override the data path used
+
+
+  Background:
+    Given I am in an empty app
+    Given a Rakefile exists which has an environment task and loads git_friendly_dumper tasks
+    And an empty database
+    And a file named "db/dump/users/schema.rb" with:
+    """
+    create_table "users", :force => true do |t|
+      t.string   "wont_use"
+      t.string   "this_schema"
+    end
+    
+    """
+    And a file named "db/dump/users/0000/0001.yml" with:
+    """
+    --- 
+    name: shouldnt
+    surname: be_loaded
+    created_at: 2003-07-26 12:38:10
+    updated_at: 2007-07-26 12:48:10
+    id: 1
+    
+    """
+
+
+  Scenario: rake db:load with different DUMP_PATH
+    Given a file named "db/alt/dump/users/schema.rb" with:
+    """
+    create_table "users", :force => true do |t|
+      t.datetime "created_at"
+      t.datetime "updated_at"
+      t.string   "name"
+      t.string   "surname"
+    end
+
+    """
+    And a file named "db/alt/dump/users/0000/0001.yml" with:
+    """
+    ---
+    name: Fred
+    created_at: 2002-07-23 12:28:10
+    updated_at: 2004-07-22 12:18:14
+    id: 1
+    surname: Bloggs
+    
+    """
+    When I successfully run `rake db:load FORCE=1 DUMP_PATH=db/alt/dump`
+    And I refresh the database tables cache
+    Then a "users" table should exist with structure:
+      | name       | type         |
+      | id         | INTEGER      |
+      | created_at | datetime     |
+      | updated_at | datetime     |
+      | name       | varchar(255) |
+      | surname    | varchar(255) |
+    And the "users" table should match exactly:
+    | id    | name  | surname | created_at          | updated_at          |
+    | 1     | Fred  | Bloggs  | 2002-07-23 12:28:10 | 2004-07-22 12:18:14 |
+

data/features/load/default_load.feature

@@ -0,0 +1,103 @@
+Feature: Load a database
+  In order to populate my database with the dumped structure (schema) and data (fixtures) in db/dump
+  I want an easy-to-use rake task to do the heavy lifting
+
+  Background:
+    Given I am in an empty app
+    And a Rakefile exists which has an environment task and loads git_friendly_dumper tasks
+    And an empty database
+
+
+  Scenario: rake db:load 
+    Given a file named "db/dump/users/schema.rb" with:
+    """
+    create_table "users", :force => true do |t|
+      t.datetime "created_at"
+      t.datetime "updated_at"
+      t.string   "name"
+      t.string   "surname"
+    end
+    
+    """
+    And a file named "db/dump/users/0000/0001.yml" with:
+    """
+    --- 
+    name: Jane
+    created_at: 2003-07-26 12:38:10
+    updated_at: 2007-07-26 12:48:10
+    id: 1
+    surname: Heidie
+    
+    """
+    And a file named "db/dump/users/0001/0008.yml" with:
+    """
+    --- 
+    name: Ethel
+    created_at: 2008-07-26 19:38:10
+    updated_at: 2010-03-22 11:38:10
+    id: 10008
+    surname: Smith
+    """
+
+    And a file named "db/dump/debts/schema.rb" with:
+    """
+    create_table "debts", :force => true do |t|
+      t.string   "name"
+      t.integer  "amount"
+    end
+    
+    """
+    And a file named "db/dump/debts/0000/0012.yml" with:
+    """
+    --- 
+    name: Jane Heidie
+    id: 12
+    amount: 3403
+    
+    """
+
+    And a file named "db/dump/schema_migrations/schema.rb" with:
+    """
+    create_table "schema_migrations", :force => true do |t|
+      t.string   "version"
+    end
+    
+    """
+    And a file named "db/dump/schema_migrations/0000/0001.yml" with:
+    """
+    --- 
+    version: "01001010123"
+    id: 1
+    
+    """
+
+    When I successfully run `rake db:load FORCE=1`
+    And I refresh the database tables cache
+    Then a "users" table should exist with structure:
+      | name       | type         |
+      | id         | INTEGER      |
+      | created_at | datetime     |
+      | updated_at | datetime     |
+      | name       | varchar(255) |
+      | surname    | varchar(255) |
+    And the "users" table should match exactly:
+      | id    | name  | surname | created_at          | updated_at          |
+      | 1     | Jane  | Heidie  | 2003-07-26 12:38:10 | 2007-07-26 12:48:10 |
+      | 10008 | Ethel | Smith   | 2008-07-26 19:38:10 | 2010-03-22 11:38:10 |
+
+    And a "debts" table should exist with structure:
+      | name   | type         |
+      | id     | INTEGER      |
+      | name   | varchar(255) |
+      | amount | integer      |
+    And the "debts" table should match exactly:
+      | id | name        | amount |
+      | 12 | Jane Heidie | 3403   |
+
+    And a "schema_migrations" table should exist with structure:
+      | name    | type         |
+      | id      | INTEGER      |
+      | version | varchar(255) |
+    And the "schema_migrations" table should match exactly:
+      | id    | version      |
+      | 1     | 01001010123  |

data/features/load/load_and_raise_error.feature

@@ -0,0 +1,97 @@
+Feature: Toggle halting load when runtime errors occur
+  RAISE_ERROR=false|0    toggle halt on runtime errors    (default true)
+  Useful for loading dev databases - don't use in production!
+
+  Background:
+    Given I am in an empty app
+    Given a Rakefile exists which has an environment task and loads git_friendly_dumper tasks
+    And an empty database
+
+
+  Scenario Outline: if a schema isn't found it always blows up, ignoring RAISE_ERROR
+    When I run `rake db:load FORCE=1 TABLES=doesnotexist RAISE_ERROR=<RAISE_ERROR>`
+    Then the exit status should be <EXIT_STATUS>
+    And the output should contain "No such file or directory"
+
+    Scenarios: always raises
+    | RAISE_ERROR | EXIT_STATUS |
+    |             | 1           |
+    | false       | 1           |
+    | 0           | 1           |
+    | true        | 1           |
+    | 1           | 1           |
+
+
+
+  Scenario Outline: using RAISE_ERROR to toggle raising ActiveRecord insertion errors
+    Given a file named "db/dump/users/schema.rb" with:
+    """
+    create_table "users", :force => true do |t|
+      t.datetime "created_at"
+      t.datetime "updated_at"
+      # t.string   "name"
+      t.string   "surname"
+    end
+    """
+    And a file named "db/dump/users/0000/0001.yml" with:
+    """
+    ---
+    name: Jane
+    created_at: 2003-07-26 12:38:10
+    updated_at: 2007-07-26 12:48:10
+    id: 1
+    surname: Heidie
+    """
+
+    When I run `rake db:load FORCE=1 TABLES=users RAISE_ERROR=<RAISE_ERROR>`
+    Then the exit status should be <EXIT_STATUS>
+    And the output <SEE_MESSAGE> contain "SQLite3::SQLException: table users has no column named name:"
+
+    Scenarios: don't raise
+    | RAISE_ERROR | EXIT_STATUS | SEE_MESSAGE |
+    | false       | 0           | should not  |
+    | 0           | 0           | should not  |
+
+    Scenarios: raise
+    | RAISE_ERROR | EXIT_STATUS | SEE_MESSAGE |
+    |             | 1           | should      |
+    | true        | 1           | should      |
+    | 1           | 1           | should      |
+
+  Scenario Outline: can also silence errors loading a fixture
+    Given a file named "db/dump/users/schema.rb" with:
+    """
+    create_table "users", :force => true do |t|
+      t.datetime "created_at"
+      t.datetime "updated_at"
+      t.string   "name"
+      t.string   "surname"
+    end
+    """
+    And I successfully run `rake db:load FORCE=1`
+
+    When I write to "db/dump/users/0000/0001.yml" with:
+    """
+    ---
+    forename: Jane
+    created_at: 2003-07-26 12:38:10
+    updated_at: 2007-07-26 12:48:10
+    id: 1
+    surname: Heidie
+    """
+    And I run `rake db:data:load FORCE=1 FIXTURES='users/0000/0001.yml' RAISE_ERROR=<RAISE_ERROR>`
+    Then the exit status should be <EXIT_STATUS>
+    And the output <SEE_MESSAGE> contain "SQLite3::SQLException: table users has no column named forename:"
+
+    Scenarios: don't raise
+    | RAISE_ERROR | EXIT_STATUS | SEE_MESSAGE |
+    | false       | 0           | should not  |
+    | 0           | 0           | should not  |
+
+    Scenarios: raise
+    | RAISE_ERROR | EXIT_STATUS | SEE_MESSAGE |
+    |             | 1           | should      |
+    | true        | 1           | should      |
+    | 1           | 1           | should      |
+
+

data/features/load/load_fixtures.feature

@@ -0,0 +1,159 @@
+Feature: Load fixtures
+  In order to load particular backups into my database
+  I want to pass the rake task a list of specific fixtures to be imported
+  FIXTURES -- specific fixture files to load, invalid argument for dump tasks
+
+  Background:
+    Given I am in an empty app
+    And a Rakefile exists which has an environment task and loads git_friendly_dumper tasks
+    And an empty database
+    And the database has a "users" table:
+      | name (string) | surname (string) |
+      | Fred          | Bloggs           |
+      | Ethel         | Smith            |
+      | Jane          | Heidie           |
+    And a file named "db/dump/users/0000/0001.yml" with:
+    """
+    --- 
+    name: Frodo
+    id: 1
+    surname: Bloggo
+    """
+    And a file named "db/dump/users/0000/0002.yml" with:
+    """
+    --- 
+    name: Ethelene
+    id: 2
+    surname: Smithy
+    """
+    
+    
+  Scenario: can't use rake db:load FIXTURES=…
+    When I run `rake db:load FIXTURES=users/0000/0001.yml FORCE=true`
+    Then the exit status should be 1
+    And the "users" table should match exactly:
+      | id | name  | surname |
+      | 1  | Fred  | Bloggs  |
+      | 2  | Ethel | Smith   |
+      | 3  | Jane  | Heidie  |
+    And the output should contain "if :fixtures option given, neither :include_schema nor :clobber_fixtures"
+  
+  
+  Scenario: can't use rake db:data:load FIXTURES=… CLOBBER_FIXTURES=true
+    When I run `rake db:load FIXTURES=users/0000/0001.yml CLOBBER_FIXTURES=true FORCE=true`
+    Then the exit status should be 1
+    And the output should contain "if :fixtures option given, neither :include_schema nor :clobber_fixtures"
+
+
+  Scenario: trying to load with FIXTURES and FIXTURES_FILE should raise an error
+    When I run `rake db:data:load FIXTURES_FILE=foo FIXTURES=notes/0000/0001.yml FORCE=true`
+    Then the exit status should be 1
+    And the output should contain "GitFriendlyDumper cannot specify both :fixtures and :fixtures_file"
+
+  
+  Scenario: loading specific fixtures into an existing table with records only replaces the ones I specify
+    When I successfully run `rake db:data:load FIXTURES=users/0000/0001.yml FORCE=true`
+    And the "users" table should match exactly:
+      | id | name  | surname |
+      | 1  | Frodo | Bloggo  |
+      | 2  | Ethel | Smith   |
+      | 3  | Jane  | Heidie  |
+
+
+
+  Scenario: loading a fixture which does not exist deletes its record
+    When I successfully run `rake db:data:load FIXTURES=users/0000/0003.yml FORCE=true`
+    And the "users" table should match exactly:
+      | id | name  | surname |
+      | 1  | Fred  | Bloggs  |
+      | 2  | Ethel | Smith   |
+
+    
+    
+  
+  Scenario: inserting a non-existant record from fixture
+    Given a file named "db/dump/users/0000/0011.yml" with:
+    """
+    --- 
+    name: Bob
+    id: 11
+    surname: Smith
+    """
+  
+    When I successfully run `rake db:data:load FIXTURES=users/0000/0011.yml FORCE=true`
+    And the "users" table should match exactly:
+      | id | name  | surname |
+      | 1  | Fred  | Bloggs  |
+      | 2  | Ethel | Smith   |
+      | 3  | Jane  | Heidie  |
+      | 11 | Bob   | Smith   |
+
+
+
+  Scenario: Updating, Creating & Deleting all in one go
+    Given a file named "db/dump/users/0000/0011.yml" with:
+    """
+    --- 
+    name: Bob
+    id: 11
+    surname: Smith
+    """
+
+    When I successfully run `rake db:data:load FIXTURES=users/0000/0001.yml,users/0000/0003.yml,users/0000/0011.yml FORCE=true`
+    And the "users" table should match exactly:
+      | id | name  | surname |
+      | 1  | Frodo | Bloggo  |
+      | 2  | Ethel | Smith   |
+      | 11 | Bob   | Smith   |
+
+
+  Scenario: specifying fixtures via a fixtures_file
+    Given a file named "db/dump/users/0000/0011.yml" with:
+    """
+    --- 
+    name: Bob
+    id: 11
+    surname: Smith
+    """
+    
+    And a file named "db/dump/fixtures" with:
+    """
+    users/0000/0001.yml
+    users/0000/0003.yml
+    users/0000/0011.yml
+    """
+    
+    When I successfully run `rake db:data:load FIXTURES_FILE=db/dump/fixtures FORCE=true`
+    Then the "users" table should match exactly:
+      | id | name  | surname |
+      | 1  | Frodo | Bloggo  |
+      | 2  | Ethel | Smith   |
+      | 11 | Bob   | Smith   |
+
+
+  Scenario: TABLES can be used whitelist a subset of the FIXTURES to operate on
+    Given the database has a "notes" table:
+      | body (string) |
+      | Get milk      |
+      | Buy Meat      |
+    And a file named "db/dump/notes/0000/0001.yml" with:
+    """
+    --- 
+    body: Get cheese
+    id: 1
+    """
+    
+    When I successfully run `rake db:data:load TABLES=notes FIXTURES=notes/0000/0001.yml,users/0000/0001.yml,users/0000/0003.yml,users/0000/0011.yml FORCE=true`
+    Then the "notes" table should match exactly:
+      | id | body       |
+      | 1  | Get cheese |
+      | 2  | Buy Meat   |
+    And the "users" table should match exactly:
+      | id | name  | surname |
+      | 1  | Fred  | Bloggs  |
+      | 2  | Ethel | Smith   |
+      | 3  | Jane  | Heidie  |  
+  
+  
+  Scenario: FIXTURES should be able to be specified as a file, instead of an env var
+  

data/features/load/load_git_changes.feature

@@ -0,0 +1,17 @@
+Feature: Figure out git changes since last load
+  In order to speed up loading, when using a git based dump
+  I want to be able to load fixtures changes since last load
+ 
+  Scenario: rake db:data:load SINCE_REF=<git ref> loads fixtures since then
+
+  Scenario: rake db:data:load SINCE_REF=<git ref> borks if DUMP_PATH aint a git repo
+  
+  Scenario: rake db:data:load SINCE_LAST_LOAD=true loads fixtures since last load
+
+  Scenario: rake db:data:load SINCE_LAST_LOAD=true borks if no last_load_ref exists in DUMP_PATH
+
+  Scenario: rake db:data:load creates a last_load_ref in DUMP_PATH
+  
+  Scenario: rake db:data:load WRITE_LAST_LOAD_REF=false doesn't create a last_load_ref
+  
+  

data/features/load/load_specific_tables.feature

@@ -0,0 +1,119 @@
+Feature: Load specific tables
+  In order to only restore particular tables from the dump to my database
+  I want to specify a list of table names for the rake task to process
+  TABLES=comma,sep,list  tables to dump/load       (default all)
+
+
+  Background:
+    Given I am in an empty app
+    And a Rakefile exists which has an environment task and loads git_friendly_dumper tasks
+    And an empty database
+
+    Given a file named "db/dump/users/schema.rb" with:
+    """
+    create_table "users", :force => true do |t|
+      t.datetime "created_at"
+      t.datetime "updated_at"
+      t.string   "name"
+      t.string   "surname"
+    end
+    
+    """
+    And a file named "db/dump/users/0000/0001.yml" with:
+    """
+    --- 
+    name: Jane
+    created_at: 2003-07-26 12:38:10
+    updated_at: 2007-07-26 12:48:10
+    id: 1
+    surname: Heidie
+    
+    """
+    And a file named "db/dump/users/0001/0008.yml" with:
+    """
+    --- 
+    name: Ethel
+    created_at: 2008-07-26 19:38:10
+    updated_at: 2010-03-22 11:38:10
+    id: 10008
+    surname: Smith
+    """
+
+    And a file named "db/dump/debts/schema.rb" with:
+    """
+    create_table "debts", :force => true do |t|
+      t.string   "name"
+      t.integer  "amount"
+    end
+    
+    """
+    And a file named "db/dump/debts/0000/0012.yml" with:
+    """
+    --- 
+    name: Jane Heidie
+    id: 12
+    amount: 3403
+    
+    """
+
+    And a file named "db/dump/schema_migrations/schema.rb" with:
+    """
+    create_table "schema_migrations", :force => true do |t|
+      t.string   "version"
+    end
+    
+    """
+    And a file named "db/dump/schema_migrations/0000/0001.yml" with:
+    """
+    --- 
+    version: "01001010123"
+    id: 1
+    
+    """
+
+
+
+    Scenario: load the debts table only
+      When I successfully run `rake db:load FORCE=1 TABLES=debts`
+      Then the database should have tables:
+        | debts |
+      But the database should not have table "users"
+      But the database should not have table "schema_migrations"
+      And a "debts" table should exist with structure:
+        | name   | type         |
+        | id     | INTEGER      |
+        | name   | varchar(255) |
+        | amount | integer      |
+      And the "debts" table should match exactly:
+        | id | name        | amount |
+        | 12 | Jane Heidie | 3403   |
+
+
+
+    Scenario: load the users and debts tables
+      When I successfully run `rake db:load FORCE=1 TABLES=debts,users`
+      Then the database should have tables:
+        | debts |
+        | users |
+      But the database should not have table "schema_migrations"
+
+      Then a "users" table should exist with structure:
+        | name       | type         |
+        | id         | INTEGER      |
+        | created_at | datetime     |
+        | updated_at | datetime     |
+        | name       | varchar(255) |
+        | surname    | varchar(255) |
+      And the "users" table should match exactly:
+        | id    | name  | surname | created_at          | updated_at          |
+        | 1     | Jane  | Heidie  | 2003-07-26 12:38:10 | 2007-07-26 12:48:10 |
+        | 10008 | Ethel | Smith   | 2008-07-26 19:38:10 | 2010-03-22 11:38:10 |
+
+      And a "debts" table should exist with structure:
+        | name   | type         |
+        | id     | INTEGER      |
+        | name   | varchar(255) |
+        | amount | integer      |
+      And the "debts" table should match exactly:
+        | id | name        | amount |
+        | 12 | Jane Heidie | 3403   |