data_migrate 2.2.0 → 3.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 6983740ef87afeb4aa83f557c1f42e5e4f062223
-  data.tar.gz: 91e0c313ec9ec3fed6b3483a94c35fefac8789f7
+  metadata.gz: 0b408b7360d8bf4c8d9eae51ede9bcd9f2e15a44
+  data.tar.gz: 89eeaec81959c73838e764006d2eecb558fca925
 SHA512:
-  metadata.gz: abdb401fd44de7e22a1cb5b310cea84b147d95a4790f6b2b7dc6e33e878d9f42c8d94a4e73f7759d06550a2814f3133510c6a4bcfd43e6761366f2a045780775
-  data.tar.gz: 69c8dcef142680e1109d75ee2cced9b5179bb5dc6ba8216a0c62fca6926e6f63023644f98885981a372c065c9265162985874f5dbc989480d9a530c381fed945
+  metadata.gz: 328b8f8c3e1f33277bf3ece1abd0b4a8a602ec9f0ff982dfa788e7e157f4f76507ba8e18c15c3ce636bbe932f7864040ae5381ada8cb5664cd8adf514b3b70fc
+  data.tar.gz: 7517e1f6bd66f96c7d503e463c9c1249d89f33160d6bf0a4a7998b9adc8a21a5b9faf16489542018f568386b1fb5528971120db3467bb27464426350424ef747

data/Changelog.md

@@ -1,6 +1,11 @@
 Changelog
 =========
 
+## 3.0.0
+
+`--skip-schema-migration` removed deprecated. This gem will no longer generate schema
+migrations. It still supports running schema/data migrations with one command.
+
 ## 2.2.0
 
 ([bilby91](https://github.com/bilby91)) Capistrano support

data/README.md

@@ -6,7 +6,7 @@ Data Migrate
 
 Run data migrations alongside schema migrations.
 
-Data migrations are stored in db/data. They act like schema
+Data migrations are stored in `db/data`. They act like schema
 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.
@@ -35,7 +35,7 @@ just the text. "Frist!!1!1" rules the day. Given that you:
 - drop the Comment model
 - fix all your test/controller/view mojo.
 
-You've just got bit.  When you rake setup:development, the mess gets
+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
@@ -56,25 +56,17 @@ test your migration, so you have the choice of `db:migrate:with_data` or
 What's it do?
 -------------
 
-Data migrations are stored in db/data. They act like schema
+Data migrations are stored in `db/data`. They act like schema
 migrations, except they should be reserved for data migrations. For
 instance, if you realize you need to titleize all yours titles, this
 is the place to do it. Running any of the provided rake tasks also
 creates a data schema table to mirror the usual schema migrations
 table to track all the goodness.
 
-Data migrations can be created at the same time as schema migrations,
-or independently.  Database (db:) tasks have been added and extended
-to run on data migrations only, or in conjunction with the schema
-migration.  For instance, `rake db:migrate:with_data` will run both
-schema and data migrations in the proper order.
-
-Note: If a data and schema migration share the same version number, schema gets precedence when migrating up. Data does down.
-
 Rails Support
 --------------------
 
-Rails 3.1: Version 1.2 supports Rails 3.1.0 and higher **but** is not longer maintained.
+Rails 3.1: Version 1.2 supports Rails 3.1.0 and higher **but** is no longer maintained.
 
 Rails 4: Version 2.0 supports Rails 4.0 and higher
 
@@ -113,15 +105,6 @@ You can generate a data migration as you would a schema migration:
 
     rails g data_migration add_this_to_that
 
-By default, the migration also generates a schema migration by the same name.
-This allows you to do things like:
-
-    rails g data_migration add_this_to_that this:string
-
-If you need a data only migration, either run it as such, with the skip-schema-migration flag:
-
-    rails g data_migration add_this_to_that --skip-schema-migration
-
 ### Rake Tasks
 
     $> rake -T data
@@ -146,15 +129,6 @@ Tasks work as they would with the 'vanilla' db version.  The 'with_data' additio
 
 With 'up' and 'down', you can specify the option 'BOTH', which defaults to false. Using true, will migrate both the data and schema (in the desired direction) if they both match the version provided.  Again, going up, schema is given precedence. Down its data.
 
-For more example, assume you have the 2 files:
-  db/migrate/20110419021211_add_x_to_y.rb
-  db/data/20110419021211_add_x_to_y.rb
-
-Running `rake db:migrate:up:with_data VERSION=20110419021211` would execute the 'db/migrate' version.
-Running `rake db:migrate:up:with_data VERSION=20110419021211` would execute the 'db/migrate' version, followed by the 'db/data' version.
-
-Going down instead of up would be the opposite.
-
 `rake db:migrate:status:with_data` provides and additional column to indicate which type of migration.
 
 Capistrano Support

data/data_migrate.gemspec

@@ -8,7 +8,7 @@ Gem::Specification.new do |s|
   s.platform    = Gem::Platform::RUBY
   s.authors     = ["Andrew J Vargo", "Ilya Katz"]
   s.email       = ["ajvargo@computer.org", "ilyakatz@gmail.com"]
-  s.homepage    = "http://ajvargo.com"
+  s.homepage    = "https://github.com/ilyakatz/data-migrate"
   s.summary     = %q{Rake tasks to migrate data alongside schema changes.}
   s.description = %q{Rake tasks to migrate data alongside schema changes.}
   s.license     = "MIT"
@@ -21,4 +21,8 @@ Gem::Specification.new do |s|
   s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
   s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
   s.require_paths = ["lib"]
+
+  s.post_install_message = %q{
+Note: --skip-schema-migration option is no longer available as of version 3.0.0
+}
 end

data/lib/data_migrate/version.rb

@@ -1,3 +1,3 @@
 module DataMigrate
-    VERSION = '2.2.0'.freeze
+    VERSION = '3.0.0'.freeze
 end

data/lib/generators/data_migration/data_migration_generator.rb

@@ -8,18 +8,15 @@ module DataMigrate
       namespace "data_migration"
       include Rails::Generators::Migration
 
-      argument :attributes, :type => :array, :default => [], :banner => "field:type field:type"
-      class_option :skip_schema_migration, :desc => 'Dont generate database schema migration file.', :type => :boolean
+      argument :attributes, type: :array, default: [], banner: 'field:type field:type'
 
       def create_data_migration
         set_local_assigns!
-        unless  options.skip_schema_migration?
-          migration_template "migration.rb", "db/migrate/#{file_name}.rb"
-        end
-        migration_template "data_migration.rb", "db/data/#{file_name}.rb"
+        migration_template 'data_migration.rb', "db/data/#{file_name}.rb"
       end
 
       protected
+
       attr_reader :migration_action
 
       def self.next_migration_number(dirname)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: data_migrate
 version: !ruby/object:Gem::Version
-  version: 2.2.0
+  version: 3.0.0
 platform: ruby
 authors:
 - Andrew J Vargo
@@ -9,20 +9,20 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-08-15 00:00:00.000000000 Z
+date: 2016-09-22 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'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - '>='
       - !ruby/object:Gem::Version
         version: '4.0'
 description: Rake tasks to migrate data alongside schema changes.
@@ -33,7 +33,7 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".gitignore"
+- .gitignore
 - Changelog.md
 - Gemfile
 - LICENSE
@@ -54,27 +54,29 @@ files:
 - lib/generators/data_migration/templates/migration.rb
 - tasks/.gitkeep
 - tasks/databases.rake
-homepage: http://ajvargo.com
+homepage: https://github.com/ilyakatz/data-migrate
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message: |2
+
+  Note: --skip-schema-migration option is no longer available as of version 3.0.0
 rdoc_options: []
 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.2.3
+rubygems_version: 2.0.14.1
 signing_key: 
 specification_version: 4
 summary: Rake tasks to migrate data alongside schema changes.