aspgems-redhillonrails_core 2.0.0.beta1

data/CHANGELOG

@@ -0,0 +1,194 @@
+[REVISION 20110112]
+
+[REMOVE] Remove unused columns monkeypatch and avoid a query to get the indexes of a table that cost so much in tables with so many records
+
+[REVISION 20080701]
+
+[FIXED] Looking up schema version fails on Rails 2.1.
+
+[REVISION 20080318]
+
+[FIXED] Case-insensitive text columns not recognised.
+
+[REVISION 20080221]
+
+[NEW] PostgreSQL view management via create_view and drop_view.
+
+[REVISION 20080209]
+
+[FIXED] PostgreSQL columns named the same as database keywords (eg. type, column, user, etc.) caused NoSuchMethod errors during model validation.
+
+[REVISION 20080110]
+
+[FIXED] Workaround for bug in MySQL that adversely affects INFORMATION schema performance take 3 (Michael Latta).
+
+[REVISION 20080103]
+
+[FIXED] Workaround for bug in MySQL that adversely affects INFORMATION schema performance take 2 (Michael Latta).
+
+[REVISION 20080102]
+
+[FIXED] Workaround for bug in MySQL that adversely affects INFORMATION schema performance (Michael Latta).
+
+[REVISION 20071128]
+
+[FIXED] Workaround to ensure plugin is only ever loaded once.
+
+[REVISION 20071013]
+
+[NEW] Rake task (db:comments) to show database table comments.
+
+[REVISION 20071013]
+
+[NEW] New migration script methods: set_table_comment and clear_table_comment. Implemented for MySQL and PostgreSQL. Currently not written to schema.rb.
+
+[REVISION 20070905]
+
+[NEW] Explicitly ignore add_foreign_key() and remove_foreign_key() when running under SQLite. This solves issues when migrating schema from other databases.
+
+[REVISION 20070707]
+
+[NEW] Make the table name in table definition accessible.
+
+[REVISION 20070529]
+
+[FIXED] Undefined constant errors when patching connection adapters. Rails now only loads the connection adapter for the specified database (it used to load them all).
+
+[REVISION 20070503]
+
+[NEW] Support for SQL92 [NOT] DEFERRABLE on foreign keys.
+[CHANGED] Foreign key names are now assigned by the database unless an explicit name is given (using :name).
+
+[REVISION 20070221]
+
+[NEW] Where possible, determine if a column is case sensitive (or not) based on the presence of case-insensitive indexes.
+
+[REVISION 20070220]
+
+[CHANGED] :ignore_case => true option when creating indexes change to :case_sensitive => false in keeping with the new Rails 1.2 option of the same name on validates_uniqueness_of. You may need to re-create your schema.rb (by using rake db:schema:dump) to pickup the new syntax.
+
+[FIXED] Multi-column, case-insensitive indexes only selecting one of the columns!
+
+[REVISION 20070219]
+
+[FIXED] Can't drop table referenced in a foreign-key. All reverse foreign keys are now dropped before dropping the table.
+
+[CHANGED] Upgrade to Rails 1.2.2.
+
+[REVISION 20070217]
+
+[NEW] Support reverse_foreign_keys for MySQL using the (typically bastardised) MySQL flavour of information_schema.
+
+[CHANGED] Merged ForiegnKey and ForeignKeyDefinition as they were practically the same.
+
+[REVISION 20070214]
+
+[NEW] :name option when creating foreign keys.
+
+[FIXED] Foreign key names are preserved in schema dumps. This means they will be copied from one database to another rather than leaving it up to the target database to make one up.
+
+[NEW] Foreign keys are automatically assigned a name (fkey_<tablename>_col1_and_col2_and_col3) if none is specified.
+
+[REVISION 20061206]
+
+[NEW] Added :ignore_case option to add_index in PostgreSQL to support case-insensitive indexes. The generated indexes are actually expression indexes of the form: lower(column_name).
+
+[REVISION 20061206]
+
+[NEW] reverse_foreign_keys methods.
+
+[REVISION 20061202]
+
+[CHANGED] Use Rails 1.2 alias_method_chain.
+
+[CHANGED] Separate modules into individual files.
+
+[REVISION 20061129]
+
+[FIXED] Foreign-key ON DELETE and ON UPDATE flipped in schema dump.
+
+[REVISION 20061121]
+
+[FIXED] MySQL doesn't support SQL92 'DROP CONSTRAINT SYNTAX'; use 'DROP FOREIGN KEY' instead.
+
+[REVISION 20061116]
+
+[FIXED] 'DROP FOREIGN KEY' should be 'DROP CONSTRAINT'.
+
+[REVISION 20061114]
+
+[CHANGED] Removed Column.required as it didn't handle updates correctly. Instead we now have Column.required_on which returns an appropriate event (nil, :save, :update).
+
+[REVISION 20061110]
+
+[FIXED] MySQL driver uses single AND double quotes around identifiers.
+
+[REVISION 20061028]
+
+[FIXED] Syntax error when generating schema under MySQL when a foreign key specifies both ON UPDATE and ON DELETE.
+
+[REVISION 20061024]
+
+[FIXED] Foreign key associations for key-word table-names are quoted in postgresql.
+
+[REVISION 20061011]
+
+[NEW] ActiveRecord::Base.base_class? returns true if the class is a base class; false otherwise.
+
+[REVISION 20061009]
+
+[NEW] ActiveRecord::Base.abstract_class? returns true if class name starts with 'Abstract'; false otherwise.
+
+[REVISION 20061001]
+
+[NEW] remove_foreign_key for completeness.
+
+[FIXED] MySQL barfs when attempting to drop a column that participates in a foreign key constraint.
+
+[REVISION 20060921]
+
+[FIXED] add_foreign_key doesn't support on_delete or on_update--It doesn't do anything with the options hash.
+
+[REVISION 20060919]
+
+[CHANGED] Column.unique is now derived based on the presence of Column.unique_scope (which is an empty array for single column unique indexes).
+
+[REVISION 20060915]
+
+[NEW] Unique columns contain scoping meta-data for multi-column unique indexes. The column to be marked as unique is either the last column not ending in '_id' or simply the last column. This follows the typical composite unique index column ordering where the scoping is specified first but will attempt to find the last non-foreign-key column just-in-case. Eg, both add_index :states, [:country_id, :name] and add_index :states, [:name, :country_id] would result in the name column marked as unique with a scope of [:country_id].
+
+[REVISION 20060913]
+
+[NEW] Column.required: returns true if a column is marked as not allowing null and has no default.
+
+[REVISION 20060911]
+
+[NEW] Patch rails MysqlColumn so that empty string defaults are treated as nil when a column is marked as NOT NULL. This primarily affects schema dumps incorrectly assigning a default of 0 to numbers and '' to strings when none was originally specified.
+
+[REVISION 20060909]
+
+[CHANGED] Renamed from Foreign Key Support.
+
+[NEW] ActiveRecord::Base.indexes.
+
+[REVISION 20060906]
+
+[FIXED] :on_update with :on_delete producing invalid SQL.
+
+[REVISION 20060905]
+
+[NEW] Schema dumper outputs foreign keys when available.
+
+[NEW] Foreign-key meta-data for: PostgreSQL; and MySQL. (Still needs a bit of DRY-ing up but it works which is the first step.)
+
+[REVISION 20060901]
+
+[FIXED] Incorrect generation of ON UPDATE/ON DELETE clauses.
+
+[NEW] Support :restrict in ON UPDATE/ON DELETE clauses.
+
+[NEW] Preliminary support for querying foreign-keys in PostgreSQL.
+
+[REVISION 20060831]
+
+[NEW] Initial version.

data/Gemfile

@@ -0,0 +1,3 @@
+source :rubygems
+
+gemspec

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2006 RedHill Consulting, Pty. Ltd.
+
+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

@@ -0,0 +1,161 @@
+= Disclaimer
+
+redhillonrails_core was originally created by http://github.com/harukizaemon but it was retired and is no longer supported.
+
+That fork is intended to make redhillonrails_core compatible with edge rails and introduce some new features.
+
+= RedHill on Rails Core
+
+Goal of redhillonrails_core is to provided missing ActiveRecord support for database specific features:
+
+* foreign_keys
+* case-insensitive and partial indexes (pgsql only)
+* views
+
+== Installation
+
+As a gem
+
+  gem install aspgems-redhillonrails_core
+
+== Compatibility
+
+* Ruby - 1.8, 1.9
+* ActiveRecord - 2.X, 3.X
+* Databases - PostgreSQL, MySQL, SQLite3 (most features should also run on others)
+
+=== Foreign Key Support
+
+The plugin provides two mechanisms for adding foreign keys as well as
+preserving foreign keys when performing a schema dump. (Using SQL-92 syntax and
+as such should be compatible with most databases that support foreign-key
+constraints.)
+
+The first mechanism for creating foreign-keys allows you to add a foreign key
+when defining a table. For example:
+
+  create_table :orders do |t|
+    ...
+    t.foreign_key :customer_id, :customers, :id
+  end
+
+You also have the option of specifying what to do on delete/update using
+<code>:on_delete</code>/<code>:on_update</code>, respectively to one of: <code>:cascade</code>; <code>:restrict</code>; and <code>:set_null</code>:
+
+  create_table :orders do |t|
+    ...
+    t.foreign_key :customer_id, :customers, :id, :on_delete => :set_null, :on_update => :cascade
+  end
+
+The second method allows you to create arbitrary foreign-keys at any time:
+
+  add_foreign_key(:orders, :customer_id, :customers, :id, :on_delete => :set_null, :on_update => :cascade)
+
+In either case, if your database supports deferred foreign keys (for example PostgreSQL) you can specify this as well:
+
+  t.foreign_key :customer_id, :customers, :id, :deferrable => true
+  add_foreign_key(:orders, :customer_id, :customers, :id, :deferrable => true)
+
+By default, the foreign key will be assigned a name by the underlying database. However, if this doesn't suit
+your needs, you can override the default assignment using the <code>:name</code> option:
+
+  add_foreign_key(:orders, :customer_id, :customers, :id, :on_delete => :set_null, :on_update => :cascade, <strong>:name => :orders_customer_id_foreign_key<strong>)
+
+You can also query the foreign keys for a model yourself by calling <code>foreign_keys()</code>:
+
+  Order.foreign_keys
+
+Or for an arbitrary table by calling <code>foreign_keys(table_name)</code> on a database adapter.
+
+Either method returns an array of the following meta-data:
+
+* +name+ - The name of the foreign key constraint;
+* +table_name+ - The table for which the foreign-key was generated;
+* +column_names+ - The column names in the table;
+* +references_table_name+ - The table referenced by the foreign-key; and
+* +references_column_names+ - The columns names in the referenced table.
+
+If you need to drop a foreign-key, use:
+
+  remove_foreign_key :orders, :orders_ordered_by_id_fkey
+
+The plugin also ensures that all foreign keys are output when performing a
+schema dump. This happens automatically when running <code>rake migrate</code> or
+<code>rake db:schema:dump</code>. This has particular implications when running
+unit tests that contain fixtures. To ensure the test data is correctly reset after
+each test, you should list your fixtures in order of parent->child. For example:
+
+  fixtures :customers, :products, :orders, :order_lines
+
+Rails will then set-up and tear-down the fixtures in the correct sequence.
+
+Some databases (PostgreSQL and MySQL for example) allow you to set a comment for a
+table. You can do this for existing tables by using:
+
+  set_table_comment :orders, "All pending and processed orders"
+
+or even at the time of creation:
+
+  create_table :orders, :comment => "All pending and processed orders" do |t|
+    ...
+  end
+
+You can clear table comments using:
+
+  clear_table_comment :orders
+
+There is also a rake tasks to show all database tables and their comments:
+
+  rake db:comments
+
+The plugin fully supports and understands the following active-record
+configuration properties:
+
+* <code>config.active_record.pluralize_table_names</code>
+* <code>config.active_record.table_name_prefix</code>
+* <code>config.active_record.table_name_suffix</code>
+
+=== View Support
+
+The plugin provides a mechanism for creating and dropping views as well as
+preserving views when performing a schema dump:
+
+  create_view :normal_customers, "SELECT * FROM customers WHERE status = 'normal'"
+  drop_view :normal_customers
+
+=== Model Indexes
+
+ActiveRecord::Base already provides a method on connection for obtaining the
+indexes for a given table. This plugin now makes it possible to obtain the
+indexes for a given model--<code>ActiveRecord::Base</code>--class. For example:
+
+  Invoice.indexes
+
+Would return all the indexes for the +invoices+ table.
+
+=== Schema Defining
+
+The plugin also adds a method--<code>defining?()</code>--to
+<code>ActiveRecord::Schema</code> to indicate when <code>define()</code> is running. This is necessary
+as some migration plugins must change their behaviour accordingly.
+
+=== Case-insensitive Indexes
+
+For PostgreSQL, you can add an option <code>:case_sensitive => false</code> to <code>add_index</code>
+which will generate an expression index of the form:
+
+  LOWER(column_name)
+
+This means finder queries of the form:
+
+  WHERE LOWER(column_name) = LOWER(?)
+
+are able to use the indexes rather require, in the worst case, full-table scans.
+
+Note also that this ties in well with Rails built-in support for case-insensitive searching:
+
+  validates_uniqueness_of :name, :case_sensitive => false
+
+=== See Also
+
+* Foreign Key Migrations (foreign_key_migrations)

data/Rakefile

@@ -0,0 +1,59 @@
+require 'bundler'
+Bundler::GemHelper.install_tasks
+
+require 'rspec/core/rake_task'
+%w[postgresql mysql mysql2 sqlite3].each do |adapter|
+  namespace adapter do
+    RSpec::Core::RakeTask.new(:spec) do |spec|
+      spec.rspec_opts = "-Ispec/connections/#{adapter}"
+    end
+  end
+end
+
+desc 'Run postgresql and mysql tests'
+task :spec do
+  %w[postgresql mysql mysql2 sqlite3].each do |adapter|
+    Rake::Task["#{adapter}:spec"].invoke
+  end
+end
+
+task :default => :spec
+
+namespace :postgresql do
+  desc 'Build the PostgreSQL test databases'
+  task :build_databases do
+    %x( createdb -E UTF8 rh_core_unittest )
+  end
+
+  desc 'Drop the PostgreSQL test databases'
+  task :drop_databases do
+    %x( dropdb rh_core_unittest )
+  end
+
+  desc 'Rebuild the PostgreSQL test databases'
+  task :rebuild_databases => [:drop_databases, :build_databases]
+end
+
+task :build_postgresql_databases => 'postgresql:build_databases'
+task :drop_postgresql_databases => 'postgresql:drop_databases'
+task :rebuild_postgresql_databases => 'postgresql:rebuild_databases'
+
+MYSQL_DB_USER = 'rh_core'
+namespace :mysql do
+  desc 'Build the MySQL test databases'
+  task :build_databases do
+    %x( echo "create DATABASE rh_core_unittest DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_unicode_ci " | mysql --user=#{MYSQL_DB_USER})
+  end
+
+  desc 'Drop the MySQL test databases'
+  task :drop_databases do
+    %x( mysqladmin --user=#{MYSQL_DB_USER} -f drop rh_core_unittest )
+  end
+
+  desc 'Rebuild the MySQL test databases'
+  task :rebuild_databases => [:drop_databases, :build_databases]
+end
+
+task :build_mysql_databases => 'mysql:build_databases'
+task :drop_mysql_databases => 'mysql:drop_databases'
+task :rebuild_mysql_databases => 'mysql:rebuild_databases'

data/init.rb

@@ -0,0 +1 @@
+require 'redhillonrails_core' unless defined?(RedHillConsulting::Core)

data/lib/redhillonrails_core.rb

@@ -0,0 +1,46 @@
+#require 'active_record/migration'
+require 'active_support/core_ext/module/attribute_accessors'
+
+module RedhillonrailsCore
+  mattr_accessor :loaded_into_rails_core
+
+  module ActiveRecord
+    extend ActiveSupport::Autoload
+
+    autoload :Base
+    autoload :Schema
+    autoload :SchemaDumper
+
+    module ConnectionAdapters
+      extend ActiveSupport::Autoload
+
+      autoload_under 'abstract' do
+        autoload :IndexDefinition
+        autoload :TableDefinition
+        autoload :Column
+        autoload :ForeignKeyDefinition
+        autoload :SchemaStatements
+      end
+
+      autoload :AbstractAdapter
+      autoload :PostgresqlAdapter
+      autoload :MysqlAdapter
+      autoload :MysqlColumn
+      autoload :Sqlite3Adapter
+    end
+  end
+
+  unless loaded_into_rails_core
+    ::ActiveRecord::Base.send(:include, RedhillonrailsCore::ActiveRecord::Base)
+    ::ActiveRecord::Schema.send(:include, RedhillonrailsCore::ActiveRecord::Schema)
+    ::ActiveRecord::SchemaDumper.send(:include, RedhillonrailsCore::ActiveRecord::SchemaDumper)
+    ::ActiveRecord::ConnectionAdapters::IndexDefinition.send(:include, RedhillonrailsCore::ActiveRecord::ConnectionAdapters::IndexDefinition)
+    ::ActiveRecord::ConnectionAdapters::TableDefinition.send(:include, RedhillonrailsCore::ActiveRecord::ConnectionAdapters::TableDefinition)
+    ::ActiveRecord::ConnectionAdapters::Column.send(:include, RedhillonrailsCore::ActiveRecord::ConnectionAdapters::Column)
+    ::ActiveRecord::ConnectionAdapters::AbstractAdapter.send(:include, RedhillonrailsCore::ActiveRecord::ConnectionAdapters::AbstractAdapter)
+    ::ActiveRecord::ConnectionAdapters::SchemaStatements.send(:include, RedhillonrailsCore::ActiveRecord::ConnectionAdapters::SchemaStatements)
+
+    self.loaded_into_rails_core = true
+  end
+end
+