migration_data 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 3832601395165ae09ded4ba1609528ae1743142e
+  data.tar.gz: 2ad9a69f0b54b83b0aa9f86ea5b91fe80726358a
+SHA512:
+  metadata.gz: bbde24c5b3c6a5a998438c41411be08472823725f7e89ddbaa38ba055775d4ef109c76e3ae02f0b545b922926ee3c52794fe9ee0d84ab4b586dd276dfddba93e
+  data.tar.gz: 02fe7cd0bf6b53c5327b9206b5432d63520cdb0c37530e0b665ccaa71a2b79ff35810bb96c81c77d2fba8e9c539c0648f9923364199319c5300ea5c39a85a265

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in migration_data.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2014 Andrey Koleshko
+
+MIT License
+
+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.md

@@ -0,0 +1,71 @@
+# MigrationData
+
+This gem provides functionality to write any code in migrations safely without regression.
+
+Sometimes we have to write some Rails code in the migrations and it's hard to
+keep them in working state because models wich are used there changes too often. there
+some techniques which help to avoid these pitfalls. For example, define model
+classes in the migrations or write raw SQL. But they don't help in 100% cases anyway.
+This gem promises to solve the problem in a simple way.
+
+Currently the gem supports Rails 4 and Ruby >= 2.0.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+    gem 'migration_data'
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install migration_data
+
+## Usage
+
+Just define in your migration `data` method:
+
+```ruby
+class CreateUsers < ActiveRecord::Migration
+  def change
+    # Database schema changes as usual
+  end
+
+  def data
+    User.create!(name: 'Andrey', email: 'ka8725@gmail.com')
+  end
+end
+```
+
+That's it. Now when you run migrations with the `rake db:migrate` command the `data` method will be run on `up`.
+
+NOTE: it's not run on `down`. If you have any reason to do it please fell free to make pull request.
+
+## Testing migrations
+
+To keep your migrations working don't forget to write test foe them.
+Possible `RSpec` test for the migration looks like this:
+
+```ruby
+require 'spec_helper'
+require Rails.root.join(ActiveRecord::Migrator.migrations_paths).join('20130906111511_create_users.rb')
+
+desribe CreateUsers do
+  describe '#data' do
+    it 'works' do
+      expect { CreateUsers.new.data }.to_not raise_exception
+    end
+  end
+end
+```
+
+## Contributing
+
+1. Fork it ( http://github.com/ka8725/migration_data/fork )
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1,15 @@
+require "bundler/gem_tasks"
+
+
+require 'rake/testtask'
+
+desc 'Default: run unit tests.'
+task default: :test
+
+desc 'Test the migration_data plugin.'
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'lib'
+  t.libs << 'test'
+  t.pattern = 'test/**/*_test.rb'
+  t.verbose = true
+end

data/lib/migration_data.rb

@@ -0,0 +1,12 @@
+require 'migration_data/version'
+
+module MigrationData
+  def exec_migration(conn, direction)
+    super
+    if direction == :up && respond_to?(:data)
+      data
+    end
+  end
+end
+
+ActiveRecord::Migration.prepend(MigrationData)

data/lib/migration_data/version.rb

@@ -0,0 +1,3 @@
+module MigrationData
+  VERSION = '0.0.1'
+end

data/migration_data.gemspec

@@ -0,0 +1,29 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'migration_data/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "migration_data"
+  spec.version       = MigrationData::VERSION
+  spec.authors       = ["Andrey Koleshko"]
+  spec.email         = ["ka8725@gmail.com"]
+  spec.summary       = %q{Provides possibility to write any code in migrations safely without regression.}
+  spec.description   = %q{Sometimes we have to write some Rails code in the migrations and it's hard to
+                          keep them in working state because models wich are used there changes too often. there
+                          some techniques which help to avoid these pitfalls. For example, define model
+                          classes in the migrations or write raw SQL. But they don't help in 100% cases anyway.
+                          This gem promises to solve the problem in a simple way.}
+  spec.homepage      = ""
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files`.split($/)
+  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
+  spec.test_files    = spec.files.grep(%r{^(test)/})
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency 'bundler', '~> 1.5'
+  spec.add_development_dependency 'rake'
+  spec.add_development_dependency 'sqlite3'
+  spec.add_dependency 'activerecord', '~> 4.0'
+end

data/test/migration_test.rb

@@ -0,0 +1,31 @@
+require 'minitest/autorun'
+require 'active_record'
+require 'migration_data'
+
+ActiveRecord::Base.establish_connection(adapter: 'sqlite3', database: 'tmp/test.sqlite3')
+
+class MyMigration < ActiveRecord::Migration
+  attr_reader :migrated_data
+
+  def data
+    @migrated_data = true
+  end
+end
+
+describe MyMigration do
+  before do
+    @migration = MyMigration.new
+  end
+
+  describe '#migrate' do
+    it 'runs #data on up direction' do
+      @migration.migrate(:up)
+      assert @migration.migrated_data
+    end
+
+    it "doesn't run #data on down direction" do
+      @migration.migrate(:down)
+      assert_nil @migration.migrated_data
+    end
+  end
+end

metadata

@@ -0,0 +1,116 @@
+--- !ruby/object:Gem::Specification
+name: migration_data
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+platform: ruby
+authors:
+- Andrey Koleshko
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2014-01-28 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.5'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.5'
+- !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: 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: activerecord
+  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: |-
+  Sometimes we have to write some Rails code in the migrations and it's hard to
+                            keep them in working state because models wich are used there changes too often. there
+                            some techniques which help to avoid these pitfalls. For example, define model
+                            classes in the migrations or write raw SQL. But they don't help in 100% cases anyway.
+                            This gem promises to solve the problem in a simple way.
+email:
+- ka8725@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- lib/migration_data.rb
+- lib/migration_data/version.rb
+- migration_data.gemspec
+- test/migration_test.rb
+homepage: ''
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+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: 
+rubygems_version: 2.2.0
+signing_key: 
+specification_version: 4
+summary: Provides possibility to write any code in migrations safely without regression.
+test_files:
+- test/migration_test.rb
+has_rdoc: