datum 0.9.2 → 4.0.0

data/lib/datum/verification_task.rb

@@ -1,154 +0,0 @@
-module Datum
-  # some reports of connections / settings issues. 
-  # verify allows for a full check of the datum db scenarios
-  # intended to be used as part of enable to report datum readiness
-  class VerificationTask
-
-
-    def disable_user_questions
-      @@ask_user = false
-    end    
-
-    def rock
-      
-      puts "\n### !!!Datum Verification !!!"
-      puts "### !!!This command DROPS the Datum Database!!!"
-
-      if @@ask_user
-        puts "\n>>>>>>>>>>>>>>>> Proceed with Datum Verification? y/n"
-        continue = STDIN.gets.chomp
-        unless continue == 'y' || continue == 'yes'
-          puts "\n ... Canceling Datum Verification\n "
-          exit!
-        end
-      end
-      
-      database_ready = false
-      database_removed = false
-      files_removed = false
-
-      begin
-        dbtsks = DbTasks.new
-        puts "\n Dropping Existing Datum Database...\n "
-        dbtsks.drop
-        puts "\n Drop complete\n "
-        puts "\n Verifing Datum functionality...\n "
-        dbtsks.create 
-        puts "   >> Database created"
-        copy_verification_files
-        puts "   >> Directories verified\n "
-        dbtsks.migrate
-        database_ready = true 
-        puts "   >> Migration complete"
-        seed_verification_table
-        puts "   >> Storage verified"
-        puts "   >> Attempting data driven test cases from database"
-        exec_test
-        puts "   >> Database driven test complete"
-        dbtsks.dump
-        puts "   >> Fixtures generated"
-        remove_verification_table_data
-        dbtsks.load
-        puts "   >> Fixture data uploaded"
-        dbtsks.localize({:table => "datum_versions"})
-        puts "   >> Localization complete"
-        dbtsks.drop
-        database_removed = true
-        puts "   >> Database dropped"
-        puts "   >> Attempting data driven test cases from file"
-        exec_test
-        puts "   >> Data file driven test complete"
-        remove_verification_files
-        files_removed = true
-        puts " \n ... Core Datum functionality verified!\n "
-      rescue Exception => exc
-        puts "   >> !!!! Verification failed !!!!"
-        puts "#{exc}"
-        puts "\n### !!! Please file email datum@tyemill.com with the above output !!!"
-      ensure
-        remove_verification_table_data if database_ready && !database_removed
-        remove_verification_files unless files_removed 
-      end
-    end
-
-    protected
-
-    def seed_verification_table
-      DatumVersion.create([
-        {:version => "0.0.1"},
-        {:version => "0.8.0"},
-        {:version => "0.8.1"},
-        {:version => "0.8.2"},
-        {:version => "0.8.3"},
-        {:version => "0.8.4"},
-        {:version => "0.8.5"},
-        {:version => "0.8.6"},
-        {:version => "0.8.7"},
-        {:version => "0.9.0"},
-        {:version => "0.9.1"},
-        {:version => "0.9.2"}])
-    end
-
-    def exec_test
-      puts "   >> Starting data-driven test cases...\n "
-      result = system "ruby -Itest #{@@test_src}"
-      raise 'Datum Testcases did not complete successfully!' if !result
-      puts "\n "
-    end
-
-    def remove_verification_table_data
-      DatumVersion.delete_all
-    end
-
-    def copy_verification_files
-      # need to make sure all existing fixtures are moved to prevent
-      # overwritting or unwanted data in verification process
-      FileUtils.cp_r "#{@@local_path}", "#{@@datum_tmp}"
-      FileUtils.remove_dir "#{@@local_path}"
-      (Datum::EnableTask.new).create_directories
-
-      FileUtils.cp_r @@migration_src, "#{@@local_path}/migrate"
-      FileUtils.cp_r @@model_src, "#{@@local_path}/models"
-      FileUtils.cp_r @@test_src, "#{@@unit_dir}"
-    end
-
-    # delete: the migration, the fixture, the ruby file, the model
-    def remove_verification_files
-
-      # need to move fixtures back
-      FileUtils.remove_dir "#{@@local_path}"
-      FileUtils.cp_r "#{@@datum_tmp}", "#{@@local_path}"
-      FileUtils.remove_dir "#{@@datum_tmp}"
-
-      files = [@@test_drop]
-      files.each { |file|
-        context.log "Removing file: #{file}"
-        FileUtils.remove_file file  
-      }
-      
-    end
-
-    private
-    @@ask_user = true
-    @@local_path = "#{Rails.root}/test/lib/datum"
-    @@datum_tmp = "#{Rails.root}/test/lib/datum_tmp"
-    @@gem_path = File.expand_path(File.dirname(__FILE__))
-    @@migration_file = "20120726105125_create_datum_versions.rb"
-    @@version_str = "DatumVersion"
-    @@version_tbl = @@version_str.tableize
-    @@version_single = @@version_tbl.singularize  
-    @@model_file = "#{@@version_single}.rb"
-    @@fixture_file = "#{@@version_tbl}.yml"
-    @@test_file = "#{@@version_single}_test.rb"
-    @@ruby_file = "#{@@version_tbl}.rb"
-    @@migration_src = "#{@@gem_path}/verify_helpers/#{@@migration_file}"
-    @@model_src = "#{@@gem_path}/verify_helpers/#{@@model_file}"
-    @@test_src = "#{@@gem_path}/verify_helpers/#{@@test_file}"
-    @@unit_dir = "#{Rails.root}/test/unit"
-    @@test_drop = "#{@@unit_dir}/#{@@test_file}"
-
-    def context
-      return Datum::Context
-    end
-  end
-end

data/lib/datum/verify_helpers/20120726105125_create_datum_versions.rb

@@ -1,18 +0,0 @@
-# used to help verify basic datum functionality
-# see rake datum:db:verify for details
-class CreateDatumVersions < ActiveRecord::Migration
-  
-  ActiveRecord::Base.establish_connection :datum
-  ActiveRecord::Base.connection.initialize_schema_migrations_table
-   
-  def self.up
-    create_table :datum_versions do |t|
-      t.string :version
-      t.timestamps
-    end
-  end
-
-  def self.down
-    drop_table :datum_versions
-  end
-end

data/lib/datum/verify_helpers/datum_version.rb

@@ -1,8 +0,0 @@
-# used to help verify basic datum functionality
-# see rake datum:db:verify for details
-class DatumVersion < ActiveRecord::Base
-  establish_connection :datum
-  
-  attr_accessible :version
-  
-end

data/lib/datum/verify_helpers/datum_version_test.rb

@@ -1,11 +0,0 @@
-
-# simple test for Datum functionality verification
-require 'test_helper'
-
-class DatumVersionTest < ActiveSupport::TestCase
-
-  test "datum versions should be accessible" do
-    drive_with :datum_versions
-    str = datum.version
-  end
-end

data/lib/generators/datum/datum_generator.rb

@@ -1,104 +0,0 @@
-require 'rails/generators/migration'
-require 'rails/generators/generated_attribute'
-
-# Generator code was modified from https://github.com/ryanb/nifty-generators/
-# Nifty Generators is Copyright (c) 2011 Ryan Bates and distributed via the
-# MIT License
-class DatumGenerator < Rails::Generators::Base
-  include Rails::Generators::Migration
-  no_tasks { attr_accessor :scaffold_name, :model_attributes}
-  source_root File.expand_path('../templates', __FILE__)
-  
-  argument :scaffold_name, :type => :string, :required => true, :banner => 'ModelName'
-  argument :args_for_m, :type => :array, :default => [], :banner => 'model:attributes'
-  
-  class_option :skip_migration, 
-  :desc => 'Don\'t generate migration file for model.', :type => :boolean
-  
-  class_option :skip_model, 
-  :desc => 'Don\'t generate a model or migration file.', :type => :boolean
-  
-  def initialize(*args, &block)
-    super
-    print_usage unless scaffold_name.underscore =~ /^[a-z][a-z0-9_\/]+$/
-    
-    @datum_path = "test/lib/datum"
-    @model_attributes = []
-    @skip_model = options.skip_model?
-
-    args_for_m.each do |arg|
-      if arg.include?(':')
-        @model_attributes << Rails::Generators::GeneratedAttribute.new(*arg.split(':'))
-      end
-    end
-
-    @model_attributes.uniq!
-
-    if @model_attributes.empty?
-      @skip_model = true # skip model if no attributes
-      if model_exists?
-        model_columns_for_attributes.each do |column|
-          @model_attributes << Rails::Generators::GeneratedAttribute.new(
-          column.name.to_s, column.type.to_s)
-        end
-      else
-        @model_attributes << Rails::Generators::GeneratedAttribute.new(
-        'name', 'string')
-      end
-    end
-  end
-  
-  def create_model
-    unless @skip_model
-      template 'datum_model.rb', "#{@datum_path}/models/#{model_path}.rb"
-    end
-  end
-  def create_migration
-    unless @skip_model || options.skip_migration?
-      migration_template 'datum_migration.rb', 
-      "#{@datum_path}/migrate/create_#{model_path.pluralize.gsub('/', '_')}.rb"
-    end
-  end
-  
-private
-
-  def plural_name
-    scaffold_name.underscore.pluralize
-  end
-  
-  def plural_class_name
-    plural_name.camelize
-  end
-  
-  def table_name
-    if scaffold_name.include?('::') && @namespace_model
-      plural_name.gsub('/', '_')
-    end
-  end
-  
-  def class_name
-    scaffold_name.split('::').last.camelize
-  end
-  
-  def model_path
-    class_name.underscore
-  end
-  
-  def model_exists?
-    File.exist? destination_path("#{@datum_path}/models/#{singular_name}.rb")
-  end
-  
-  def destination_path(path)
-    File.join(destination_root, path)
-  end
-  
-  # FIXME: Should be proxied to ActiveRecord::Generators::Base
-  # Implement the required interface for Rails::Generators::Migration.
-  def self.next_migration_number(dirname) #:nodoc:
-    if ActiveRecord::Base.timestamped_migrations
-      Time.now.utc.strftime("%Y%m%d%H%M%S")
-    else
-      "%.3d" % (current_migration_number(dirname) + 1)
-    end
-  end
-end

data/lib/generators/datum/templates/datum_migration.rb

@@ -1,21 +0,0 @@
-
-class Create<%= class_name.pluralize.delete('::') %> < ActiveRecord::Migration
-  
-  ActiveRecord::Base.establish_connection :datum
-  ActiveRecord::Base.connection.initialize_schema_migrations_table
-  
-  def self.up
-    create_table :<%= table_name || plural_name.split('/').last %> do |t|
-    <%- for attribute in model_attributes -%>
-      t.<%= attribute.type %> :<%= attribute.name %>
-    <%- end -%>
-    <%- unless options[:skip_timestamps] -%>
-      t.timestamps
-    <%- end -%>
-    end
-  end
-
-  def self.down
-    drop_table :<%= table_name || plural_name.split('/').last %>
-  end
-end

data/lib/generators/datum/templates/datum_model.rb

@@ -1,6 +0,0 @@
-
-class <%= class_name %> < ActiveRecord::Base
-  establish_connection :datum
-<%= "  set_table_name :#{table_name}\n" if table_name -%>
-  attr_accessible <%= model_attributes.map { |a| ":#{a.name}" }.join(", ") %>
-end

data/lib/tasks/datum.rake

@@ -1,49 +0,0 @@
-require "datum/verification_task"
-require "datum/enable_task"
-require "datum/db_tasks"
-
-namespace :datum do
-  
-  desc "Enable datum functionality"
-  task :enable => :environment do
-    (Datum::EnableTask.new).rock
-  end
-
-  namespace :db do
-
-    desc "Create datum database"
-    task :create => :environment do invoke "create" end
-    
-    desc "Migrate datum database"
-    task :migrate => :environment do invoke "migrate" end
-    
-    desc "Drop datum database"
-    task :drop => :environment do invoke "drop" end
-    
-    desc "Dump data as fixtures from datum database"
-    task :dump => :environment do invoke "dump" end
-    
-    desc "Loads datum fixtures IF table is empty"
-    task :load_when_empty => :environment do invoke "load_when_empty" end
-
-    desc "Loads fixtures specific to datum database"
-    task :load => :environment do invoke "load" end
-
-    desc "Prepares datum for use via create, migrate, load"
-    task :prepare => :environment do invoke "prepare" end
-    
-    #desc "Quick verification of basic datum functionality"
-    #task :verify do invoke "verify" end
-    
-    desc "Enables datum execution without database dependency"
-    task :localize, [:table] => [:environment] do |t, args|
-      (Datum::DbTasks.new).localize args
-    end
-    
-    private
-    def invoke method
-      (Datum::DbTasks.new).send(method)
-    end
-    
-  end
-end

data/test/datum_test.rb

@@ -1,17 +0,0 @@
-require 'test_helper'
-require 'rake'
-
-class DatumTest < ActiveSupport::TestCase
-  
-  #test "db_migrate should migrate" do
-   # puts "this is the second test...."
-    #    Rake.application.rake_require "tasks/datum"
-    #    DatumTasks.migrate
-    #    assert_equal 0, 1, "Nope"
-    #    puts "... Path: #{Rails.env}"
-  #end
-  
-#  test "truth" do
-#    assert_kind_of Module, Datum
-#  end
-end

data/test/dummy/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.

data/test/dummy/Rakefile

@@ -1,7 +0,0 @@
-#!/usr/bin/env rake
-# Add your own tasks in files placed in lib/tasks ending in .rake,
-# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
-
-require File.expand_path('../config/application', __FILE__)
-
-Dummy::Application.load_tasks

data/test/dummy/app/assets/javascripts/application.js

@@ -1,15 +0,0 @@
-// This is a manifest file that'll be compiled into application.js, which will include all the files
-// listed below.
-//
-// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
-// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
-//
-// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
-// the compiled file.
-//
-// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
-// GO AFTER THE REQUIRES BELOW.
-//
-//= require jquery
-//= require jquery_ujs
-//= require_tree .