datashift 0.11.1 → 0.12.0

data/.document

@@ -1,5 +0,0 @@
-lib/**/*.rb
-bin/*
-- 
-features/**/*.feature
-LICENSE.txt

data/spec/fixtures/ProjectsDefaults.yml

@@ -1,29 +0,0 @@
-## YAML Template.
-
-# Format is :
-#  --- !ruby/object:ActiveRecordModel
-#   :datashift_defaults
-#       :key value
-#
-
-Project: 
-  datashift_defaults: 
-    value_as_string: "Default Project Value"
-  category: reference:category_002
-  
-  datashift_overrides: 
-    value_as_double: 99.23546
-  
---- !ruby/object:Project 
-attributes: 
-  id:
-  title: 
-  value_as_string: "" 
-  value_as_text:  "object has value text"
-  value_as_boolean:
-  value_as_datetime: 
-  value_as_integer: 23
-  value_as_double: 45.82
-  created_at: 
-  updated_at: 
-

data/spec/fixtures/config/database.yml

@@ -1,28 +0,0 @@
-# Used by spec helper to build test databases
-# These entires can be used in call to db_connect ( see spec_helper )
-
-<% adapter = 'sqlite3' %>
-<% adapter = 'jdbcsqlite3' if(DataShift::Guards::jruby? ) %>
-
-test_mysql:
-  adapter: jdbcmysql
-  database: datashift_test_models_db
-  username: test
-  password: test
-  host: localhost
-
-test_memory:
-  adapter: <%= adapter %>
-  database: :memory
-
-test_file:
-  adapter: <%= adapter %>
-  database: <%= File.join(fixtures_path(), 'db', 'datashift_test_models_db.sqlite') %>
-  encoding: utf8
-  host: localhost
-
-test_spree_standalone:
-  adapter: <%= adapter %>
-  database: <%= File.join(fixtures_path(), 'db', 'datashift_Spree_db.sqlite') %>
-  encoding: utf8
-  host: localhost

data/spec/fixtures/db/migrate/20110803201325_create_test_bed.rb

@@ -1,96 +0,0 @@
-# Author ::   Tom Statter
-# Date ::     Aug 2011
-# License::   MIT
-#
-# Details::   Migration to create a test database that exercises all aspects of Active Record models
-#
-
-class CreateTestBed < ActiveRecord::Migration
-  
-  def self.up
-
-    create_table :users do |t|
-      t.string   :title
-      t.string   :first_name
-    end
-    
-    # belongs_to  :user
-    # has many :milestones
-    #
-    create_table :projects do |t|
-      t.string   :title
-      t.string   :value_as_string
-      t.text     :value_as_text
-      t.boolean  :value_as_boolean, :default => false
-      t.datetime :value_as_datetime, :default => nil
-      t.integer  :value_as_integer, :default => 0
-      t.decimal  :value_as_double, :precision => 8, :scale => 2, :default => 0.0
-      t.references :user
-      t.timestamps
-    end
-
-    # belongs_to  :project
-    # @project => has_many :milestones
-    
-    create_table :milestones do |t|
-      t.string     :name
-      t.datetime   :datetime, :default => nil
-      t.decimal    :cost, :precision => 8, :scale => 2, :default => 0.0
-      t.references :project
-      t.timestamps
-    end
-
-    # belongs_to  :project, project => has_one
-    create_table :owners do |t|
-      t.string   :name
-      t.references :project
-      t.timestamps
-    end
-
-    # has_belongs_to_many :project
-    create_table :categories do |t|
-      t.string   :reference
-      t.timestamps
-    end
-
-    # testing has_belongs_to_many (hence no id)
-    create_table :categories_projects, :id => false do |t|
-      t.references :category
-      t.references :project
-    end
-
-    create_table :versions do |t|
-      t.string   :name
-      t.timestamps
-    end
-
-    # testing project has_many release + versions :through
-    create_table :loader_releases do |t|
-      t.string   :name
-      t.references :project
-      t.references :version
-      t.timestamps
-    end
-
-
-    create_table :long_and_complex_table_linked_to_versions do |t|
-      t.references :version
-    end
-
-    create_table :empties do |t|
-    end
-
-  end
-
-  def self.down
-    drop_table :users
-    drop_table :projects
-    drop_table :categories
-    drop_table :loader_releases
-    drop_table :versions
-    drop_table :categories_projectss
-    drop_table :milestones
-    drop_table :long_and_complex_table_linked_to_versions
-    drop_table :empties
-  end
-end

data/spec/fixtures/db/migrate/20121009161700_add_digitals.rb

@@ -1,24 +0,0 @@
-# Author ::   Tom Statter
-# Date ::     Oct 2012
-# License::   MIT
-#
-# Details::   Migration for paperclip specs
-
-class AddDigitals < ActiveRecord::Migration
-  
-  def self.up
-
-     create_table :digitals do |t|
-      t.integer :owner_id
-      t.string  :attachment_file_name
-      t.string  :attachment_content_type
-      t.integer :attachment_file_size
-      t.timestamps
-    end
-    
-  end
-
-  def self.down
-    drop_table :digitals
-  end
-end

data/spec/fixtures/load_datashift.thor

@@ -1,3 +0,0 @@
-require 'datashift'
-
-DataShift::load_commands

data/spec/fixtures/models/category.rb

@@ -1,7 +0,0 @@
-
-
-# had_and_belongs to join table
-class Category < ActiveRecord::Base
-  has_and_belongs_to_many :projects
-end
-

data/spec/fixtures/models/digital.rb

@@ -1,14 +0,0 @@
-# To change this template, choose Tools | Templates
-# and open the template in the editor.
-
-require 'paperclip'
-
-class Digital < ActiveRecord::Base
-  
-  include Paperclip::Glue
-  
-  attr_accessible :attachment
-  
-  has_attached_file :attachment, :styles => { :medium => "300x300>", :thumb => "100x100>" }, :path => ":rails_root/private/digitals/:id/:basename.:extension"
-  
-end

data/spec/fixtures/models/empty.rb

@@ -1,2 +0,0 @@
-class Empty < ActiveRecord::Base
-end

data/spec/fixtures/models/loader_release.rb

@@ -1,10 +0,0 @@
-
-
-# Join Table with additional columns
-class LoaderRelease < ActiveRecord::Base
-  
-  belongs_to :project
-  belongs_to :version
-
-  #validate the name
-end

data/spec/fixtures/models/long_and_complex_table_linked_to_version.rb

@@ -1,6 +0,0 @@
-
-# Join Table with additional columns
-class LongAndComplexTableLinkedToVersion < ActiveRecord::Base
-
-  belongs_to :version
-end

data/spec/fixtures/models/milestone.rb

@@ -1,8 +0,0 @@
-
-
-class Milestone < ActiveRecord::Base
-  belongs_to :project
-  #validate the name, cost
-
-  delegate :title, :title=, :to => :project
-end

data/spec/fixtures/models/owner.rb

@@ -1,7 +0,0 @@
-class Owner < ActiveRecord::Base
-    
-  belongs_to :project, :dependent => :destroy
-  
-  has_many :digitals, :dependent => :destroy
-  
-end

data/spec/fixtures/models/project.rb

@@ -1,26 +0,0 @@
-# A set of models and associations we can use in our specs to test
-# basic database columns and also relationships
-
-# See Companion migration spec/db/migrate
-
-class Project < ActiveRecord::Base
-
-  has_one  :owner
-
-  has_many :milestones
-
-  has_many :loader_releases
-  has_many :versions, :through => :loader_releases
-
-
-  #has_many :release_versions, :through => :loader_releases, :source => :versions
-
-  has_and_belongs_to_many :categories
-
-  attr_accessible  :value_as_string, :value_as_boolean, :value_as_double
-  
-  def multiply
-    10 * value_as_double
-  end
-  
-end

data/spec/fixtures/models/version.rb

@@ -1,7 +0,0 @@
-
-
-class Version < ActiveRecord::Base
-  has_many :releases
-
-  has_one :long_and_complex_table_linked_to_version
-end

data/spec/fixtures/test_model_defs.rb

@@ -1,9 +0,0 @@
-
-
-# TODO investigate potential gem that might this require_all
-
-base = File.join(File.dirname(__FILE__), 'models')
-  
-Dir[ File.join(base, '*.rb') ].each do |file| 
-  require File.join(base, File.basename(file, File.extname(file) ))
-end

data/spec/rails_sandbox/.gitignore

@@ -1,15 +0,0 @@
-# See http://help.github.com/ignore-files/ for more about ignoring files.
-#
-# If you find yourself ignoring temporary files generated by your text editor
-# or operating system, you probably want to add a global ignore instead:
-#   git config --global core.excludesfile ~/.gitignore_global
-
-# Ignore bundler config
-/.bundle
-
-# Ignore the default SQLite database.
-/db/*.sqlite3
-
-# Ignore all logfiles and tempfiles.
-/log/*.log
-/tmp

data/spec/rails_sandbox/Gemfile

@@ -1,40 +0,0 @@
-source 'https://rubygems.org'
-
-gem 'rails', '3.2.8'
-
-# Bundle edge Rails instead:
-# gem 'rails', :git => 'git://github.com/rails/rails.git'
-
-gem 'activerecord-jdbcsqlite3-adapter'
-
-gem 'jruby-openssl'
-gem 'json'
-
-# Gems used only for assets and not required
-# in production environments by default.
-group :assets do
-  gem 'sass-rails',   '~> 3.2.3'
-  gem 'coffee-rails', '~> 3.2.1'
-
-  # See https://github.com/sstephenson/execjs#readme for more supported runtimes
-  gem 'therubyrhino'
-
-  gem 'uglifier', '>= 1.0.3'
-end
-
-gem 'jquery-rails'
-
-# To use ActiveModel has_secure_password
-# gem 'bcrypt-ruby', '~> 3.0.0'
-
-# To use Jbuilder templates for JSON
-# gem 'jbuilder'
-
-# Use unicorn as the app server
-# gem 'unicorn'
-
-# Deploy with Capistrano
-# gem 'capistrano'
-
-# To use debugger
-# gem 'ruby-debug'

data/spec/rails_sandbox/README.rdoc

@@ -1,261 +0,0 @@
-== Welcome to Rails
-
-Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the Model-View-Control pattern.
-
-This pattern splits the view (also called the presentation) into "dumb"
-templates that are primarily responsible for inserting pre-built data in between
-HTML tags. The model contains the "smart" domain objects (such as Account,
-Product, Person, Post) that holds all the business logic and knows how to
-persist themselves to a database. The controller handles the incoming requests
-(such as Save New Account, Update Product, Show Post) by manipulating the model
-and directing data to the view.
-
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails. You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-
-
-== Getting Started
-
-1. At the command prompt, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
-
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
-
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
-
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
-
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
-
-
-== Debugging Rails
-
-Sometimes your application goes wrong. Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-
-First area to check is the application log files. Have "tail -f" commands
-running on the server.log and development.log. Rails will automatically display
-debugging and runtime information to these files. Debugging info will also be
-shown in the browser on requests from 127.0.0.1.
-
-You can also log your own messages directly into the log file from your code
-using the Ruby logger class from inside your controllers. Example:
-
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-
-The result will be a message in your log file along the lines of:
-
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
-
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-
-Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
-several books available online as well:
-
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-
-These two books will bring you up to speed on the Ruby language and also on
-programming in general.
-
-
-== Debugger
-
-Debugger support is available through the debugger command when you start your
-Mongrel or WEBrick server with --debugger. This means that you can break out of
-execution at any point in the code, investigate and change the model, and then,
-resume execution! You need to install ruby-debug to run the server in debugging
-mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.all
-      debugger
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8
-          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
-       #<Post:0x14a6620
-          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better, you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you can enter "cont".
-
-
-== Console
-
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. Here you'll have all parts of the application
-configured, just like it is when the application is running. You can inspect
-domain models, change values, and save to the database. Starting the script
-without arguments will launch it in the development environment.
-
-To start the console, run <tt>rails console</tt> from the application
-directory.
-
-Options:
-
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-
-More information about irb can be found at:
-link:http://www.rubycentral.org/pickaxe/irb.html
-
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>rails
-dbconsole</tt>. You would be connected to the database with the credentials
-defined in database.yml. Starting the script without arguments will connect you
-to the development database. Passing an argument will connect you to a different
-database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-
-== Description of Contents
-
-The default directory structure of a generated Ruby on Rails application:
-
-  |-- app
-  |   |-- assets
-  |       |-- images
-  |       |-- javascripts
-  |       `-- stylesheets
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      |-- assets
-          `-- stylesheets
-      `-- plugins
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/assets
-  Contains subdirectories for images, stylesheets, and JavaScript files.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from
-  ApplicationController which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb. Models descend from
-  ActiveRecord::Base by default.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use
-  eRuby syntax by default.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the
-  common header/footer method of wrapping views. In your views, define a layout
-  using the <tt>layout :default</tt> and create a file named default.html.erb.
-  Inside default.html.erb, call <% yield %> to render the view using this
-  layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are
-  generated for you automatically when using generators for controllers.
-  Helpers can be used to wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database,
-  and other dependencies.
-
-db
-  Contains the database schema in schema.rb. db/migrate contains all the
-  sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when
-  generated using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that
-  doesn't belong under controllers, models, or helpers. This directory is in
-  the load path.
-
-public
-  The directory available for the web server. Also contains the dispatchers and the
-  default HTML files. This should be set as the DOCUMENT_ROOT of your web
-  server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the rails generate
-  command, template test files will be generated for you and placed in this
-  directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins
-  subdirectory. If the app has frozen rails, those gems also go here, under
-  vendor/rails/. This directory is in the load path.