data_migrate 3.1.0 → 3.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 49cdd9dd0bf6956f0581db3174d7c120cdeab467
-  data.tar.gz: ebb746af559056f2d7f8e59bb3d8d77766c9add4
+  metadata.gz: bf69bd4a2c1fb2dc456bf88df16a89b06ea7b7dd
+  data.tar.gz: 0836666a623ae289792dcba1b0422c98c9cd87cc
 SHA512:
-  metadata.gz: c88fab2799838783cfa4bd3fc44f33e6d90b4366a795baa1bfcee172b581bd270b7b6cad77695deaf21f2a431717b5e5904689c8a8d6c21fcfedeae8dd6c694a
-  data.tar.gz: a26cb2fdca59ee696f5821c48039ed8531252f543e0135bf41171a089d40a1a65578497ca0fc95b2760be4bd7816745a7ca053c2d3dfd4349d26a6188bbbb745
+  metadata.gz: 93da479ae6eb63a85d954d6a140e30578e7e511b4bec44aa0c952fb09e98e7b62bfd2f3661147872e3c08d28c245197582aa49c24012fe1615e3d680241b2d40
+  data.tar.gz: 6d11fcff914918d0b2f1f5575e9f08cfcabf16ae912a98837bcc43e5407695b75f8b7300b32bf7ead08729946fb37ec7291c386ea6066a99b598962fc5e7a65d

data/.gitignore

@@ -3,3 +3,4 @@
 *.gem
 *.lock
 gemfiles/.bundle
+spec/db

data/.travis.yml

@@ -1,7 +1,5 @@
 language: ruby
 rvm:
-  - 2.0.0-p648
-  - 2.1.10
   - 2.2.6
   - 2.3.4
 script: bundle exec rspec
@@ -10,6 +8,7 @@ gemfile:
   - gemfiles/rails_4.1.gemfile
   - gemfiles/rails_4.2.gemfile
   - gemfiles/rails_5.0.gemfile
+  - gemfiles/rails_5.1.gemfile
 matrix:
   exclude:
     - rvm: 2.0.0-p648

data/Appraisals

@@ -15,3 +15,7 @@ end
 appraise 'rails-5.0' do
   gem 'rails', '5.0.3'
 end
+
+appraise 'rails-5.1' do
+  gem 'rails', '5.1'
+end

data/Changelog.md

@@ -1,10 +1,14 @@
 Changelog
 =========
 
+## 3.2.0
+- Add support for Rails 5.1
+- No longer testing EOL rubies
+
 ## 3.1.0
 
 Rails 5.0 support thanks to
-[jturkel](https://github.com/jturkel) and [gacha](https://github.com/gacha)
+[jturkel](https://github.com/jturkel) and [abreckner](https://github.com/abreckner)
 
 ## 3.0.1
 

data/Gemfile.rails5.1

@@ -0,0 +1,5 @@
+source "http://rubygems.org"
+
+# Specify your gem's dependencies in data_migrate.gemspec
+gemspec
+gem 'rails', '~> 5.1'

data/README.md

@@ -13,6 +13,8 @@ migrations, except they should be reserved for data migrations. For
 instance, if you realize you need to titleize all your titles, this
 is the place to do it.
 
+![Travis](./screenshot.png)
+
 # Why should I use this?
 
 Its seems when a project hits a certain size, I get to manipulate data
@@ -26,35 +28,37 @@ migration.  It'd be much better to keep concerns separate. The benefit
 of having them separate has to do with your data model.
 
 For instance, lets take an absurd example, to illustrate: You have
-your infamous [Rails blog](http://media.rubyonrails.org/video/rails-0-5.mov)
-that has posts with many comments.  After some use, you decide you are
-going to be a trend setter, and want only one comment per post, and
-just the text. "Frist!!1!1" rules the day. Given that you:
-- write a migration to add a comment column to Post
-- write a migration to move the contents of the first comments to the Post
-- drop the column_id column from Post
-- drop the Comment model
-- fix all your test/controller/view mojo.
+a blog application that has posts with many comments.
+After some use, you decide you are going to be a trend setter,
+and want only one comment per post, and just the text.
+
+Given that you:
+- write a migration to add a comment column to `Post`
+- write a migration to move the contents of the first comments to the `Post`
+- drop the `column_id` column from `Post`
+- drop the `Comment` model
+- fix all your tests
 
 You've just got bit.  When you `rake setup:development`, the mess gets
 mad at you after it creates your database, and starts cranking through
 migrations.  It gets to the part where you iterate over the comments
-and it blows up.  You don't have a comment model anymore for it to
+and it blows up.  You don't have a `Comment` model anymore for it to
 even try and get 'all' from.  You think you are smarter, and wrap the
-AR call in a conditional based on the environment. That's fine until
-you get that QA gal, and she wants her own thing. Then the UI people
-get tired of waiting for the full stack to load on page refreshes, so
-you have to edit past migrations...
+ActiveRecord call in a conditional based on the environment.
+
+That's fine until you get that QA gal, and she wants her own thing.
+Then the UI people get tired of waiting for the full stack to load on page
+refreshes, so you have to edit past migrations...
 
 With Data Migrate, you have the control.  You can generate your
 migrations as schema or data as you would as your work flow. For
 setting tasks that don't require any intermediate AR activity, like
-dev and test, you stick with db:migrate.  For your prod, and qa, you
+dev and test, you stick with `db:migrate`.  For production and QA, you
 change their scripts to `db:migrate:with_data`.  Of course you want to
 test your migration, so you have the choice of `db:migrate:with_data` or
 `data:migrate` to just capture that data change.
 
-## What's it do?
+## What does it do?
 
 Data migrations are stored in `db/data`. They act like schema
 migrations, except they should be reserved for data migrations. For
@@ -71,7 +75,11 @@ Rails 4: Version 2.0 supports Rails 4.0 and higher
 
 Rails 5.0: Supported
 
-### Important note
+Rails 5.1: Supported
+
+### Important notes for older versions
+
+#### v2
 
 If you upgraded to Rails 4 while using `data_migrate` prior to version 2,
 the gem wrote data migration versions into
@@ -80,6 +88,11 @@ the gem wrote data migration versions into
 
 This may cause some unintended consequences. See [#22](https://github.com/ilyakatz/data-migrate/issues/22)
 
+#### v1
+
+If you've installed previous to v1.1.0, you'll want to delete the
+`create_data_migrations_table` migration.
+
 ## Installation
 Add the gem to your project
 
@@ -89,10 +102,9 @@ Add the gem to your project
 Then `bundle install` and you are ready to go.
 
 So you know, when you use one of the provide rake tasks, a table
-called 'data_migrations' will be created in your database. This
-is to mirror the way the standard 'db' rake tasks work. If you've
-installed previous to v1.1.0, you'll want to delete the
-'create\_data\_migrations_table' migration.
+called `data_migrations` will be created in your database. This
+is to mirror the way the standard `db` rake tasks work.
+
 
 ## Usage
 
@@ -147,6 +159,7 @@ From now on capistrano will run `rake db:migrate:with_data` in every deploy.
 Run tests for a specific version of Rails
 
 ```
+appraisal install
 appraisal rails-4.2 rspec
 appraisal rails-5.0 rspec
 ```

data/data_migrate.gemspec

@@ -15,7 +15,7 @@ Gem::Specification.new do |s|
 
   s.rubyforge_project = "data_migrate"
 
-  s.add_dependency('rails', '>= 4.0', '< 5.1')
+  s.add_dependency('rails', '>= 4.0')
   s.add_development_dependency "appraisal"
   s.add_development_dependency "rake"
   s.add_development_dependency "rspec"

data/gemfiles/rails_5.1.gemfile

@@ -0,0 +1,7 @@
+# This file was generated by Appraisal
+
+source "http://rubygems.org"
+
+gem "rails", "5.1"
+
+gemspec path: "../"

data/lib/data_migrate/version.rb

@@ -1,3 +1,3 @@
 module DataMigrate
-    VERSION = '3.1.0'.freeze
+    VERSION = '3.2.0'.freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: data_migrate
 version: !ruby/object:Gem::Version
-  version: 3.1.0
+  version: 3.2.0
 platform: ruby
 authors:
 - Andrew J Vargo
@@ -9,138 +9,132 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-06-23 00:00:00.000000000 Z
+date: 2017-08-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '4.0'
-    - - <
-      - !ruby/object:Gem::Version
-        version: '5.1'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '4.0'
-    - - <
-      - !ruby/object:Gem::Version
-        version: '5.1'
 - !ruby/object:Gem::Dependency
   name: appraisal
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rspec-core
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: pry
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rb-readline
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: sqlite3
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: timecop
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 description: Rake tasks to migrate data alongside schema changes.
@@ -151,13 +145,14 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
-- .rspec
-- .travis.yml
+- ".gitignore"
+- ".rspec"
+- ".travis.yml"
 - Appraisals
 - Changelog.md
 - Gemfile
 - Gemfile.rails5
+- Gemfile.rails5.1
 - LICENSE
 - README.md
 - Rakefile
@@ -166,6 +161,7 @@ files:
 - gemfiles/rails_4.1.gemfile
 - gemfiles/rails_4.2.gemfile
 - gemfiles/rails_5.0.gemfile
+- gemfiles/rails_5.1.gemfile
 - lib/capistrano/data_migrate.rb
 - lib/capistrano/data_migrate/migrate.rb
 - lib/data_migrate.rb
@@ -179,10 +175,10 @@ files:
 - lib/generators/data_migration/data_migration_generator.rb
 - lib/generators/data_migration/templates/data_migration.rb
 - lib/generators/data_migration/templates/migration.rb
+- screenshot.png
 - spec/data_migrate/data_migrator_spec.rb
 - spec/data_migrate/data_schema_migration_spec.rb
 - spec/data_migrate/migration.rb
-- spec/db/test.db
 - spec/generators/data_migration/data_migration_generator_spec.rb
 - spec/spec_helper.rb
 - tasks/.gitkeep
@@ -200,17 +196,17 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: data_migrate
-rubygems_version: 2.0.14.1
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: Rake tasks to migrate data alongside schema changes.
@@ -218,6 +214,5 @@ test_files:
 - spec/data_migrate/data_migrator_spec.rb
 - spec/data_migrate/data_schema_migration_spec.rb
 - spec/data_migrate/migration.rb
-- spec/db/test.db
 - spec/generators/data_migration/data_migration_generator_spec.rb
 - spec/spec_helper.rb