automigration 0.2.2 → 1.0.0

data/lib/automigration/migrator.rb

@@ -1,54 +1,34 @@
 module Automigration
   class Migrator
     mattr_reader :system_tables
-    mattr_reader :migrations_path
-    mattr_reader :models_load_path
-    mattr_reader :models_to_ignore
+    mattr_reader :migration_paths
+    mattr_reader :model_paths
     @@system_tables = []
-    @@migrations_path = nil
-    @@models_load_path = []
-    @@models_to_ignore = []
+    @@migration_paths = []
+    @@model_paths = []
 
     def self.set_system_tables(tables)
       @@system_tables = tables
     end
 
-    def self.set_migrations_path(path)
-      @@migrations_path = path
+    def self.set_migration_paths(paths)
+      @@migration_paths = paths
     end
 
-    def self.set_models_load_path(paths)
-      @@models_load_path = paths
-    end
-
-    def self.set_models_to_ignore(models)
-      @@models_to_ignore = models
-    end
-
-    def self.all_tables
-      sql = "SELECT tablename FROM pg_tables WHERE schemaname = 'public';"
-      ActiveRecord::Base.connection.execute(sql).map do |row|
-        row["tablename"]
-      end
-    end
-
-    def self.get_models
-      @@models_load_path.map do |path|
-        Dir[File.expand_path("**/*.rb", path)].map do |model_file|
-          model_name = model_file.sub(path.to_s + '/', '').sub(/.rb$/, '')
-          next if @@models_to_ignore.include?(model_name)
-          model = model_name.camelize.constantize
-          if model && model.is_a?(Class) && model.superclass == ActiveRecord::Base
-            model
-          end
-        end
-      end.flatten.compact
+    def self.set_model_paths(paths)
+      @@model_paths = paths
     end
 
     def initialize(options = {})
       options.assert_valid_keys(:skip_output, :models)
 
-      @models = options[:models] || self.class.get_models
+      @@model_paths.each do |path|
+        Dir[File.expand_path("**/*.rb", path)].each do |file|
+          require file
+        end
+      end
+
+      @models = options[:models] || ActiveRecord::Base.descendants
       @options = options
     end
 
@@ -60,86 +40,67 @@ module Automigration
       @models.each do |model|
         update_model_schema(model)
         tables << model.table_name
-
-        # update globalize2 tables
-        if model.respond_to?(:translated_attribute_names)
-          translated_model = translated_model(model)
-          update_model_schema(translated_model)
-          tables << translated_model.table_name
-        end
       end
 
       #remove unused tables
-      (self.class.all_tables - tables - @@system_tables).each do |table|
-        con.drop_table(table)
+      (connection.tables - tables - @@system_tables).each do |table|
+        connection.drop_table(table)
         log "Remove table '#{table}'", :red
       end
 
       # clean migration table
-      if con.table_exists?('schema_migrations') and @@migrations_path
+      if connection.table_exists?('schema_migrations') && !@@migration_paths.empty?
         sql = "SELECT version FROM schema_migrations;"
 
-        migrations_in_db = con.execute(sql).map{|row| row['version']}
-        current_migrations = Dir[File.expand_path("*.rb", @@migrations_path)].map do |m_file| 
-          File.basename(m_file) =~ /(\d{14})/
-          $1
+        migrations_in_db = connection.execute(sql).map{|row| row['version']}
+        current_migrations = []
+        @@migration_paths.each do |path|
+          Dir[File.expand_path("*.rb", path)].each do |m_file| 
+            File.basename(m_file) =~ /(\d{14})/
+            current_migrations << $1
+          end
         end
 
         (migrations_in_db - current_migrations).each do |m|
           log "Clean migration '#{m}'", :red
           sql = "DELETE FROM schema_migrations WHERE version = '#{m}';"
-          con.execute(sql)
+          connection.execute(sql)
         end
       end
     end
 
     private
-    def translated_model(model)
-      Class.new(ActiveRecord::Base).tap do |out|
-        out.set_table_name((model.model_name.underscore + '_translation').pluralize)
-
-        out.has_fields do |f|
-          f.integer "#{model.table_name.singularize}_id"
-          f.string :locale
-          model.translated_attribute_names.each do |attr_name|
-            model.fields_keeper.db_columns_for_field(attr_name).each do |column|
-              f.send column.type, column.name
-            end
-          end
-        end
-      end
-    end
 
     def update_model_schema(model)
       # 0. Create table if need
-      unless con.table_exists?(model.table_name)
-        con.create_table(model.table_name) {}
+      unless connection.table_exists?(model.table_name)
+        connection.create_table(model.table_name) {}
         log "Create table #{model.table_name}", :green
         model.reset_column_information
       end
 
-      unless model.fields_keeper.auto_migrable?
+      unless model.auto_migrable?
         log "#{model.to_s} skipped", :yellow
       else
         log "process #{model.to_s} ..."
-        auto_columns = model.fields_keeper.db_columns
+        auto_columns = model.field_db_columns
         auto_columns_names = auto_columns.map{|c| c.name.to_s}
         auto_columns_hash = Hash[auto_columns.map{|c| [c.name.to_s, c]}]
 
         # 1. update columns
         (model.column_names & auto_columns_names).each do |name|
-          model_column = Fields::Sys::DbColumn.from_activerecord_column(model.columns_hash[name])
+          model_column = Automigration::DbColumn.from_activerecord_column(model.columns_hash[name])
           auto_column = auto_columns_hash[name]
 
           unless model_column.the_same?(auto_column)
             begin
-              con.change_column(model.table_name, name, auto_column.type, auto_column.to_options)
+              connection.change_column(model.table_name, name, auto_column.type, auto_column.to_options)
 
               log "Update column #{name} of #{model.table_name} " + 
                 "to :#{auto_column.type} type and options #{auto_column.to_options.inspect}", :yellow
             rescue
-              con.remove_column(model.table_name, name)
-              con.add_column(model.table_name, name, auto_column.type, auto_column.to_options)
+              connection.remove_column(model.table_name, name)
+              connection.add_column(model.table_name, name, auto_column.type, auto_column.to_options)
               log "recreate column #{name} in #{model.table_name}", :yellow
             end
           end
@@ -148,7 +109,7 @@ module Automigration
         # 2. add new columns
         (auto_columns_names - model.column_names).each do |name|
           auto_column = auto_columns_hash[name]
-          con.add_column(model.table_name, name, auto_column.type, auto_column.to_options)
+          connection.add_column(model.table_name, name, auto_column.type, auto_column.to_options)
           log "Add column #{name} to #{model.table_name}", :green
 
           model.reset_column_information
@@ -160,9 +121,9 @@ module Automigration
         end
 
         # 3. remove obsoleted columns
-        not_to_del = ['id'] + model.fields_keeper.migration_attrs
+        not_to_del = ['id'] + model.migration_attrs
         (model.column_names - auto_columns_names - not_to_del).each do |name|
-          con.remove_column(model.table_name, name)
+          connection.remove_column(model.table_name, name)
           log "Remove column #{name} from #{model.table_name}", :red
         end
 
@@ -170,7 +131,7 @@ module Automigration
       end
     end
 
-    def con
+    def connection
       ActiveRecord::Base.connection
     end
 

data/lib/automigration/version.rb

@@ -1,3 +1,3 @@
 module Automigration
-  VERSION = "0.2.2"
+  VERSION = "1.0.0"
 end

data/spec/dummy/.gitignore

@@ -0,0 +1,2 @@
+/log/*.log
+/db/schema.rb

data/spec/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== 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.