backlog 0.9.1 → 0.10.0

data/vendor/rails/activerecord/lib/active_record/locking/optimistic.rb

@@ -1,137 +0,0 @@
-module ActiveRecord
-  module Locking
-    # == What is Optimistic Locking
-    #
-    # Optimistic locking allows multiple users to access the same record for edits, and assumes a minimum of 
-    # conflicts with the data.  It does this by checking whether another process has made changes to a record since
-    # it was opened, an ActiveRecord::StaleObjectError is thrown if that has occurred and the update is ignored.
-    #
-    # Check out ActiveRecord::Locking::Pessimistic for an alternative.
-    #
-    # == Usage
-    #
-    # Active Records support optimistic locking if the field <tt>lock_version</tt> is present.  Each update to the
-    # record increments the lock_version column and the locking facilities ensure that records instantiated twice
-    # will let the last one saved raise a StaleObjectError if the first was also updated. Example:
-    #
-    #   p1 = Person.find(1)
-    #   p2 = Person.find(1)
-    #   
-    #   p1.first_name = "Michael"
-    #   p1.save
-    #   
-    #   p2.first_name = "should fail"
-    #   p2.save # Raises a ActiveRecord::StaleObjectError
-    #
-    # You're then responsible for dealing with the conflict by rescuing the exception and either rolling back, merging,
-    # or otherwise apply the business logic needed to resolve the conflict.
-    #
-    # You must ensure that your database schema defaults the lock_version column to 0.
-    #
-    # This behavior can be turned off by setting <tt>ActiveRecord::Base.lock_optimistically = false</tt>.
-    # To override the name of the lock_version column, invoke the <tt>set_locking_column</tt> method.
-    # This method uses the same syntax as <tt>set_table_name</tt>
-    module Optimistic
-      def self.included(base) #:nodoc:
-        base.extend ClassMethods
-
-        base.cattr_accessor :lock_optimistically, :instance_writer => false
-        base.lock_optimistically = true
-
-        base.alias_method_chain :update, :lock
-        base.alias_method_chain :attributes_from_column_definition, :lock
-
-        class << base
-          alias_method :locking_column=, :set_locking_column
-        end
-      end
-
-      def locking_enabled? #:nodoc:
-        self.class.locking_enabled?
-      end
-
-      private
-        def attributes_from_column_definition_with_lock
-          result = attributes_from_column_definition_without_lock
-        
-          # If the locking column has no default value set,
-          # start the lock version at zero.  Note we can't use
-          # locking_enabled? at this point as @attributes may
-          # not have been initialized yet
-        
-          if lock_optimistically && result.include?(self.class.locking_column)
-            result[self.class.locking_column] ||= 0
-          end
-        
-          return result
-        end
-
-        def update_with_lock #:nodoc:
-          return update_without_lock unless locking_enabled?
-
-          lock_col = self.class.locking_column
-          previous_value = send(lock_col)
-          send(lock_col + '=', previous_value + 1)
-
-          affected_rows = connection.update(<<-end_sql, "#{self.class.name} Update with optimistic locking")
-            UPDATE #{self.class.table_name}
-            SET #{quoted_comma_pair_list(connection, attributes_with_quotes(false))}
-            WHERE #{self.class.primary_key} = #{quote_value(id)}
-            AND #{self.class.quoted_locking_column} = #{quote_value(previous_value)}
-          end_sql
-
-          unless affected_rows == 1
-            raise ActiveRecord::StaleObjectError, "Attempted to update a stale object"
-          end
-
-          return true
-        end
-
-      module ClassMethods
-        DEFAULT_LOCKING_COLUMN = 'lock_version'
-
-        def self.extended(base)
-          class <<base
-            alias_method_chain :update_counters, :lock
-          end
-        end
-
-        # Is optimistic locking enabled for this table? Returns true if the
-        # #lock_optimistically flag is set to true (which it is, by default)
-        # and the table includes the #locking_column column (defaults to
-        # lock_version).
-        def locking_enabled?
-          lock_optimistically && columns_hash[locking_column]
-        end
-
-        # Set the column to use for optimistic locking. Defaults to lock_version.
-        def set_locking_column(value = nil, &block)
-          define_attr_method :locking_column, value, &block
-          value
-        end
-
-        # The version column used for optimistic locking. Defaults to lock_version.
-        def locking_column
-          reset_locking_column
-        end
-
-        # Quote the column name used for optimistic locking.
-        def quoted_locking_column
-          connection.quote_column_name(locking_column)
-        end
-
-        # Reset the column used for optimistic locking back to the lock_version default.
-        def reset_locking_column
-          set_locking_column DEFAULT_LOCKING_COLUMN
-        end
-
-        # make sure the lock version column gets updated when counters are
-        # updated.
-        def update_counters_with_lock(id, counters)
-          counters = counters.merge(locking_column => 1) if locking_enabled?
-          update_counters_without_lock(id, counters)
-        end
-      end
-    end
-  end
-end

data/vendor/rails/activerecord/lib/active_record/locking/pessimistic.rb

@@ -1,77 +0,0 @@
-# Copyright (c) 2006 Shugo Maeda <shugo@ruby-lang.org>
-#
-# 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.
-
-
-module ActiveRecord
-  module Locking
-    # Locking::Pessimistic provides support for row-level locking using
-    # SELECT ... FOR UPDATE and other lock types.
-    #
-    # Pass :lock => true to ActiveRecord::Base.find to obtain an exclusive
-    # lock on the selected rows:
-    #   # select * from accounts where id=1 for update
-    #   Account.find(1, :lock => true)
-    #
-    # Pass :lock => 'some locking clause' to give a database-specific locking clause
-    # of your own such as 'LOCK IN SHARE MODE' or 'FOR UPDATE NOWAIT'.
-    #
-    # Example:
-    #   Account.transaction do
-    #     # select * from accounts where name = 'shugo' limit 1 for update
-    #     shugo = Account.find(:first, :conditions => "name = 'shugo'", :lock => true)
-    #     yuko = Account.find(:first, :conditions => "name = 'yuko'", :lock => true)
-    #     shugo.balance -= 100
-    #     shugo.save!
-    #     yuko.balance += 100
-    #     yuko.save!
-    #   end
-    #
-    # You can also use ActiveRecord::Base#lock! method to lock one record by id.
-    # This may be better if you don't need to lock every row. Example:
-    #   Account.transaction do
-    #     # select * from accounts where ...
-    #     accounts = Account.find(:all, :conditions => ...)
-    #     account1 = accounts.detect { |account| ... }
-    #     account2 = accounts.detect { |account| ... }
-    #     # select * from accounts where id=? for update
-    #     account1.lock!
-    #     account2.lock!
-    #     account1.balance -= 100
-    #     account1.save!
-    #     account2.balance += 100
-    #     account2.save!
-    #   end
-    #
-    # Database-specific information on row locking:
-    #   MySQL: http://dev.mysql.com/doc/refman/5.1/en/innodb-locking-reads.html
-    #   PostgreSQL: http://www.postgresql.org/docs/8.1/interactive/sql-select.html#SQL-FOR-UPDATE-SHARE
-    module Pessimistic
-      # Obtain a row lock on this record. Reloads the record to obtain the requested
-      # lock. Pass an SQL locking clause to append the end of the SELECT statement
-      # or pass true for "FOR UPDATE" (the default, an exclusive row lock).  Returns
-      # the locked record.
-      def lock!(lock = true)
-        reload(:lock => lock) unless new_record?
-        self
-      end
-    end
-  end
-end

data/vendor/rails/activerecord/lib/active_record/migration.rb

@@ -1,393 +0,0 @@
-module ActiveRecord
-  class IrreversibleMigration < ActiveRecordError#:nodoc:
-  end
-  
-  class DuplicateMigrationVersionError < ActiveRecordError#:nodoc:
-    def initialize(version)
-      super("Multiple migrations have the version number #{version}")
-    end
-  end
-  
-  # Migrations can manage the evolution of a schema used by several physical databases. It's a solution
-  # to the common problem of adding a field to make a new feature work in your local database, but being unsure of how to
-  # push that change to other developers and to the production server. With migrations, you can describe the transformations
-  # in self-contained classes that can be checked into version control systems and executed against another database that
-  # might be one, two, or five versions behind.
-  #
-  # Example of a simple migration:
-  #
-  #   class AddSsl < ActiveRecord::Migration
-  #     def self.up
-  #       add_column :accounts, :ssl_enabled, :boolean, :default => 1
-  #     end
-  #
-  #     def self.down
-  #       remove_column :accounts, :ssl_enabled
-  #     end
-  #   end
-  #
-  # This migration will add a boolean flag to the accounts table and remove it again, if you're backing out of the migration.
-  # It shows how all migrations have two class methods +up+ and +down+ that describes the transformations required to implement
-  # or remove the migration. These methods can consist of both the migration specific methods, like add_column and remove_column,
-  # but may also contain regular Ruby code for generating data needed for the transformations.
-  #
-  # Example of a more complex migration that also needs to initialize data:
-  #
-  #   class AddSystemSettings < ActiveRecord::Migration
-  #     def self.up
-  #       create_table :system_settings do |t|
-  #         t.column :name,     :string
-  #         t.column :label,    :string
-  #         t.column :value,    :text
-  #         t.column :type,     :string
-  #         t.column :position, :integer
-  #       end
-  #
-  #       SystemSetting.create :name => "notice", :label => "Use notice?", :value => 1
-  #     end
-  #
-  #     def self.down
-  #       drop_table :system_settings
-  #     end
-  #   end
-  #
-  # This migration first adds the system_settings table, then creates the very first row in it using the Active Record model
-  # that relies on the table. It also uses the more advanced create_table syntax where you can specify a complete table schema
-  # in one block call.
-  #
-  # == Available transformations
-  #
-  # * <tt>create_table(name, options)</tt> Creates a table called +name+ and makes the table object available to a block
-  #   that can then add columns to it, following the same format as add_column. See example above. The options hash is for
-  #   fragments like "DEFAULT CHARSET=UTF-8" that are appended to the create table definition.
-  # * <tt>drop_table(name)</tt>: Drops the table called +name+.
-  # * <tt>rename_table(old_name, new_name)</tt>: Renames the table called +old_name+ to +new_name+.
-  # * <tt>add_column(table_name, column_name, type, options)</tt>: Adds a new column to the table called +table_name+
-  #   named +column_name+ specified to be one of the following types:
-  #   :string, :text, :integer, :float, :decimal, :datetime, :timestamp, :time,
-  #   :date, :binary, :boolean. A default value can be specified by passing an
-  #   +options+ hash like { :default => 11 }. Other options include :limit and :null (e.g. { :limit => 50, :null => false })
-  #   -- see ActiveRecord::ConnectionAdapters::TableDefinition#column for details.
-  # * <tt>rename_column(table_name, column_name, new_column_name)</tt>: Renames a column but keeps the type and content.
-  # * <tt>change_column(table_name, column_name, type, options)</tt>:  Changes the column to a different type using the same
-  #   parameters as add_column.
-  # * <tt>remove_column(table_name, column_name)</tt>: Removes the column named +column_name+ from the table called +table_name+.
-  # * <tt>add_index(table_name, column_names, index_type, index_name)</tt>: Add a new index with the name of the column, or +index_name+ (if specified) on the column(s). Specify an optional +index_type+ (e.g. UNIQUE).
-  # * <tt>remove_index(table_name, index_name)</tt>: Remove the index specified by +index_name+.
-  #
-  # == Irreversible transformations
-  #
-  # Some transformations are destructive in a manner that cannot be reversed. Migrations of that kind should raise
-  # an <tt>IrreversibleMigration</tt> exception in their +down+ method.
-  #
-  # == Running migrations from within Rails
-  #
-  # The Rails package has several tools to help create and apply migrations.
-  #
-  # To generate a new migration, use <tt>script/generate migration MyNewMigration</tt>
-  # where MyNewMigration is the name of your migration. The generator will
-  # create a file <tt>nnn_my_new_migration.rb</tt> in the <tt>db/migrate/</tt>
-  # directory, where <tt>nnn</tt> is the next largest migration number.
-  # You may then edit the <tt>self.up</tt> and <tt>self.down</tt> methods of
-  # n MyNewMigration.
-  #
-  # To run migrations against the currently configured database, use
-  # <tt>rake migrate</tt>. This will update the database by running all of the
-  # pending migrations, creating the <tt>schema_info</tt> table if missing.
-  #
-  # To roll the database back to a previous migration version, use
-  # <tt>rake migrate VERSION=X</tt> where <tt>X</tt> is the version to which
-  # you wish to downgrade. If any of the migrations throw an
-  # <tt>IrreversibleMigration</tt> exception, that step will fail and you'll
-  # have some manual work to do.
-  #
-  # == Database support
-  #
-  # Migrations are currently supported in MySQL, PostgreSQL, SQLite,
-  # SQL Server, Sybase, and Oracle (all supported databases except DB2).
-  #
-  # == More examples
-  #
-  # Not all migrations change the schema. Some just fix the data:
-  #
-  #   class RemoveEmptyTags < ActiveRecord::Migration
-  #     def self.up
-  #       Tag.find(:all).each { |tag| tag.destroy if tag.pages.empty? }
-  #     end
-  #
-  #     def self.down
-  #       # not much we can do to restore deleted data
-  #       raise IrreversibleMigration
-  #     end
-  #   end
-  #
-  # Others remove columns when they migrate up instead of down:
-  #
-  #   class RemoveUnnecessaryItemAttributes < ActiveRecord::Migration
-  #     def self.up
-  #       remove_column :items, :incomplete_items_count
-  #       remove_column :items, :completed_items_count
-  #     end
-  #
-  #     def self.down
-  #       add_column :items, :incomplete_items_count
-  #       add_column :items, :completed_items_count
-  #     end
-  #   end
-  #
-  # And sometimes you need to do something in SQL not abstracted directly by migrations:
-  #
-  #   class MakeJoinUnique < ActiveRecord::Migration
-  #     def self.up
-  #       execute "ALTER TABLE `pages_linked_pages` ADD UNIQUE `page_id_linked_page_id` (`page_id`,`linked_page_id`)"
-  #     end
-  #
-  #     def self.down
-  #       execute "ALTER TABLE `pages_linked_pages` DROP INDEX `page_id_linked_page_id`"
-  #     end
-  #   end
-  #
-  # == Using a model after changing its table
-  #
-  # Sometimes you'll want to add a column in a migration and populate it immediately after. In that case, you'll need
-  # to make a call to Base#reset_column_information in order to ensure that the model has the latest column data from
-  # after the new column was added. Example:
-  #
-  #   class AddPeopleSalary < ActiveRecord::Migration
-  #     def self.up
-  #       add_column :people, :salary, :integer
-  #       Person.reset_column_information
-  #       Person.find(:all).each do |p|
-  #         p.update_attribute :salary, SalaryCalculator.compute(p)
-  #       end
-  #     end
-  #   end
-  #
-  # == Controlling verbosity
-  #
-  # By default, migrations will describe the actions they are taking, writing
-  # them to the console as they happen, along with benchmarks describing how
-  # long each step took.
-  #
-  # You can quiet them down by setting ActiveRecord::Migration.verbose = false.
-  #
-  # You can also insert your own messages and benchmarks by using the #say_with_time
-  # method:
-  #
-  #   def self.up
-  #     ...
-  #     say_with_time "Updating salaries..." do
-  #       Person.find(:all).each do |p|
-  #         p.update_attribute :salary, SalaryCalculator.compute(p)
-  #       end
-  #     end
-  #     ...
-  #   end
-  #
-  # The phrase "Updating salaries..." would then be printed, along with the
-  # benchmark for the block when the block completes.
-  class Migration
-    @@verbose = true
-    cattr_accessor :verbose
-
-    class << self
-      def up_with_benchmarks #:nodoc:
-        migrate(:up)
-      end
-
-      def down_with_benchmarks #:nodoc:
-        migrate(:down)
-      end
-
-      # Execute this migration in the named direction
-      def migrate(direction)
-        return unless respond_to?(direction)
-
-        case direction
-          when :up   then announce "migrating"
-          when :down then announce "reverting"
-        end
-        
-        result = nil
-        time = Benchmark.measure { result = send("#{direction}_without_benchmarks") }
-
-        case direction
-          when :up   then announce "migrated (%.4fs)" % time.real; write
-          when :down then announce "reverted (%.4fs)" % time.real; write
-        end
-        
-        result
-      end
-
-      # Because the method added may do an alias_method, it can be invoked
-      # recursively. We use @ignore_new_methods as a guard to indicate whether
-      # it is safe for the call to proceed.
-      def singleton_method_added(sym) #:nodoc:
-        return if @ignore_new_methods
-        
-        begin
-          @ignore_new_methods = true
-
-          case sym
-            when :up, :down
-              klass = (class << self; self; end)
-              klass.send(:alias_method_chain, sym, "benchmarks")
-          end
-        ensure
-          @ignore_new_methods = false
-        end
-      end
-
-      def write(text="")
-        puts(text) if verbose
-      end
-
-      def announce(message)
-        text = "#{name}: #{message}"
-        length = [0, 75 - text.length].max
-        write "== %s %s" % [text, "=" * length]
-      end
-
-      def say(message, subitem=false)
-        write "#{subitem ? "   ->" : "--"} #{message}"
-      end
-
-      def say_with_time(message)
-        say(message)
-        result = nil
-        time = Benchmark.measure { result = yield }
-        say "%.4fs" % time.real, :subitem
-        result
-      end
-
-      def suppress_messages
-        save = verbose
-        self.verbose = false
-        yield
-      ensure
-        self.verbose = save
-      end
-
-      def method_missing(method, *arguments, &block)
-        say_with_time "#{method}(#{arguments.map { |a| a.inspect }.join(", ")})" do
-          arguments[0] = Migrator.proper_table_name(arguments.first) unless arguments.empty? || method == :execute
-          ActiveRecord::Base.connection.send(method, *arguments, &block)
-        end
-      end
-    end
-  end
-
-  class Migrator#:nodoc:
-    class << self
-      def migrate(migrations_path, target_version = nil)
-        Base.connection.initialize_schema_information
-
-        case
-          when target_version.nil?, current_version < target_version
-            up(migrations_path, target_version)
-          when current_version > target_version
-            down(migrations_path, target_version)
-          when current_version == target_version
-            return # You're on the right version
-        end
-      end
-      
-      def up(migrations_path, target_version = nil)
-        self.new(:up, migrations_path, target_version).migrate
-      end
-      
-      def down(migrations_path, target_version = nil)
-        self.new(:down, migrations_path, target_version).migrate
-      end
-      
-      def schema_info_table_name
-        Base.table_name_prefix + "schema_info" + Base.table_name_suffix
-      end
-
-      def current_version
-        (Base.connection.select_one("SELECT version FROM #{schema_info_table_name}") || {"version" => 0})["version"].to_i
-      end
-
-      def proper_table_name(name)
-        # Use the ActiveRecord objects own table_name, or pre/suffix from ActiveRecord::Base if name is a symbol/string
-        name.table_name rescue "#{ActiveRecord::Base.table_name_prefix}#{name}#{ActiveRecord::Base.table_name_suffix}"
-      end
-        
-    end
-    
-    def initialize(direction, migrations_path, target_version = nil)
-      raise StandardError.new("This database does not yet support migrations") unless Base.connection.supports_migrations?
-      @direction, @migrations_path, @target_version = direction, migrations_path, target_version
-      Base.connection.initialize_schema_information
-    end
-
-    def current_version
-      self.class.current_version
-    end
-
-    def migrate
-      migration_classes.each do |(version, migration_class)|
-        Base.logger.info("Reached target version: #{@target_version}") and break if reached_target_version?(version)
-        next if irrelevant_migration?(version)
-
-        Base.logger.info "Migrating to #{migration_class} (#{version})"
-        migration_class.migrate(@direction)
-        set_schema_version(version)
-      end
-    end
-
-    private
-      def migration_classes
-        migrations = migration_files.inject([]) do |migrations, migration_file|
-          load(migration_file)
-          version, name = migration_version_and_name(migration_file)
-          assert_unique_migration_version(migrations, version.to_i)
-          migrations << [ version.to_i, migration_class(name) ] 
-        end
-
-        down? ? migrations.sort.reverse : migrations.sort
-      end
-      
-      def assert_unique_migration_version(migrations, version)
-        if !migrations.empty? && migrations.transpose.first.include?(version)
-          raise DuplicateMigrationVersionError.new(version)
-        end
-      end
-      
-      def migration_files
-        files = Dir["#{@migrations_path}/[0-9]*_*.rb"].sort_by do |f|
-          migration_version_and_name(f).first.to_i
-        end
-        down? ? files.reverse : files
-      end
-                 
-      def migration_class(migration_name)
-        migration_name.camelize.constantize
-      end
-    
-      def migration_version_and_name(migration_file)
-        return *migration_file.scan(/([0-9]+)_([_a-z0-9]*).rb/).first
-      end
-      
-      def set_schema_version(version)
-        Base.connection.update("UPDATE #{self.class.schema_info_table_name} SET version = #{down? ? version.to_i - 1 : version.to_i}")
-      end
-      
-      def up?
-        @direction == :up
-      end
-      
-      def down?
-        @direction == :down
-      end
-      
-      def reached_target_version?(version)
-        return false if @target_version == nil
-        (up? && version.to_i - 1 >= @target_version) || (down? && version.to_i <= @target_version)
-      end
-      
-      def irrelevant_migration?(version)
-        (up? && version.to_i <= current_version) || (down? && version.to_i > current_version)
-      end
-  end
-end