schema_plus 0.4.1 → 1.0.0

data/.gitignore

@@ -21,5 +21,7 @@ pkg
 ## PROJECT::SPECIFIC
 .rvmrc
 *.log
-*.sqlite3
+spec/*/*/*.sqlite3
 Gemfile.lock
+gemfiles/*.lock
+gemfiles/**/*.lock

data/.travis.yml

@@ -1,18 +1,15 @@
 rvm:
-  - 1.8.7
   - 1.9.2
   - 1.9.3
 gemfile:
-  - gemfiles/Gemfile.rails-2.3
-  - gemfiles/Gemfile.rails-3.0
-  - gemfiles/Gemfile.rails-3.1
-  - gemfiles/Gemfile.rails-3.2
+  - gemfiles/rails-3.2/Gemfile.postgresql
+  - gemfiles/rails-3.2/Gemfile.sqlite3
+  - gemfiles/rails-3.2/Gemfile.mysql
+  - gemfiles/rails-3.2/Gemfile.mysql2
 before_script:
-  - "mysql -e 'create database schema_plus_unittest;' > /dev/null"
-  - "psql -c 'create database schema_plus_unittest;' -U postgres > /dev/null"
+  - rake create_databases
 after_script:
-  - "mysql -e 'drop database schema_plus_unittest;' > /dev/null"
-  - "psql -c 'drop database schema_plus_unittest;' -U postgres > /dev/null"
+  - rake drop_databases
 env: 'POSTGRES_DB_USER=postgres MYSQL_DB_USER=""'
 notifications:
   recipients:

data/Gemfile

@@ -1,7 +1,3 @@
 source "http://rubygems.org"
 
 gemspec
-
-platforms :ruby_19 do
-  gem "ruby-debug19"
-end

data/README.rdoc

@@ -1,6 +1,5 @@
 = SchemaPlus
 
-== Overview
 
 SchemaPlus is an ActiveRecord extension that provides enhanced capabilities for schema definition and querying, including: enhanced and more DRY index capabilities, support and automation for foreign key constraints, and support for views.
 
@@ -8,14 +7,18 @@ For added rails DRYness see also the gems
 {+schema_associations+}[http://rubygems.org/gems/schema_associations] and
 {+schema_validations+}[http://rubygems.org/gems/schema_validations]
 
+{<img src="https://secure.travis-ci.org/lomba/schema_plus.png"/>}[http://travis-ci.org/lomba/schema_plus]
+{<img src="https://gemnasium.com/lomba/schema_plus.png" alt="Dependency Status" />}[https://gemnasium.com/lomba/schema_plus]
+
 == Compatibility
 
 SchemaPlus supports all combinations of:
-* rails 2.3, 3.0, or 3.1, or 3.2
-* MRI ruby 1.8.7, 1.9.2 or 1.9.3
+* rails 3.2
 * PostgreSQL, MySQL (using mysql or mysql2 gem), or SQLite3 (using sqlite3 3.7.7 which has foreign key support)
+* MRI ruby 1.9.2 or 1.9.3
 
-Support for rails 2.3 will likely be dropped eventually.
+Note: As of version 1.0.0, SchemaPlus no longer supports rails 2.3, 3.0 and 3.1 and ruby 1.8.7.  The last version
+to support them was 0.4.1.
 
 == Installation
 
@@ -45,15 +48,15 @@ With standard rails migrations, you specify indexes separately from the table de
     add_index :parts, :name     # index repeats table and column names and is defined separately
     add_index :parts, :product_code, :unique => true
 
-But with SchemaPlus you can specify your indexes when you define each column:
+But with SchemaPlus you can specify your indexes when you define each column, with options as desired
 
     # More DRY way...
     create_table :parts do |t|
       t.string :name,           :index => true
-      t.string :product_code,   :index => :unique
+      t.string :product_code,   :index => { :unique => true }
     end
 
-Options can be provided index using a hash, for example:
+The options hash can include an index name:
 
     t.string :product_code,     :index => { :unique => true, :name => "my_index_name" }
 
@@ -66,9 +69,45 @@ You can also create multi-column indexes, for example:
     t.string :area_code
     t.string :local_number      :index => { :with => [:country_code, :area_code], :unique => true }
 
-If you're using Postgresql, SchemaPlus provides support for conditions, expressions, index methods, and case-insensitive indexes; see doc at SchemaPlus::ActiveRecord::ConnectionAdapters::PostgresqlAdapter and SchemaPlus::ActiveRecord::ConnectionAdapters::IndexDefinition
+And you can specify index orders:
+
+    t.string :first_name
+    t.string :last_name,        :index => { :with => :first_name, :order => {:first_name => :desc, :last_name => :asc}}
+
+As a convenient shorthand, the :unique option can be specified as
+
+    t.string :product_code,   :index => :unique 
+
+which is equivalent to
+
+    t.string :product_code,   :index => { :unique => true }
+
+If you're using Postgresql, SchemaPlus provides support for conditions, expressions, index methods, and case-insensitive indexes:
+
+    t.string :last_name,  :index => { :conditions => 'deleted_at IS NULL' }
+    t.string :last_name,  :index => { :expression => 'upper(last_name)' }
+    t.string :last_name,  :index => { :kind => 'hash' }
+    t.string :last_name,  :index => { :case_sensitive => false }        # shorthand for :expression => 'lower(last_name)'
+
+These features are available also in ActiveRecord::Migration.add_index.  See
+doc at SchemaPlus::ActiveRecord::ConnectionAdapters::PostgresqlAdapter and
+SchemaPlus::ActiveRecord::ConnectionAdapters::IndexDefinition
+
+When you query column information using ActiveRecord::Base#columns, SchemaPlus
+analogously provides index information relevant to each column: which indexes
+reference the column, whether the column must be unique, etc.  See doc at
+SchemaPlus::ActiveRecord::ConnectionAdapters::Column
+
+SchemaPlus also tidies some index-related behavior:
+
+* Rails' various db adapters have inconsistent behavior regarding an
+  attempt to create a duplicate index: some quietly ignore the attempt,
+  some raise an error.   SchemaPlus regularizes the behavor to ignore the
+  attempt for all db adapters.
+
+* If you rename a table, indexes named using rails' automatic naming
+  convention will be renamed correspondingly.
 
-And when you query column information using ActiveRecord::Base#columns, SchemaPlus analogously provides index information relevant to each column: which indexes reference the column, whether the column must be unique, etc.  See doc at SchemaPlus::ActiveRecord::ConnectionAdapters::Column
 
 === Foreign Key Constraints
 
@@ -77,29 +116,41 @@ common convention that you name a column with suffix +_id+ to indicate that
 it's a foreign key, SchemaPlus automatically defines the appropriate
 constraint.
 
-You can explicitly specify foreign key constraints, or override the
-automatic ones, using the +:references+ option to specify the table
-name (and optionally that table's key column name, if it's not +id+).
+SchemaPlus also creates foreign key constraints for rails' <tt>t.references</tt>
+or <tt>t.belongs_to</tt>, which take the singular of the referenced table
+name and implicitly create the column suffixed with +_id+.
+
+You can explicitly specify whether or not to generate a foreign key
+constraint, and specify or override automatic options, using the
++:foreign_key+ keyword
 
 Here are some examples:
 
     t.integer :author_id                                 # automatically references table 'authors', key id
     t.integer :parent_id                                 # special name parent_id automatically references its own table (for tree nodes)
-    t.integer :author, :references => :authors           # non-conventional column name needs :references for a constraint
-    t.integer :author_id, :references => :authors          # same as automatic behavior
-    t.integer :author_id, :references => [:authors, :id]   # same as automatic behavior
-    t.integer :author_id, :references => :people         # override table name
-    t.integer :author_id, :references => [:people, :ssn] # override table name and key
-    t.integer :author_id, :references => nil              # don't create a constraint
+    t.integer :author_id, :foreign_key => true           # same as default automatic behavior
+    t.integer :author,    :foreign_key => true           # non-conventional column name needs to force creation, table name is assumed to be 'authors'
+    t.integer :author_id, :foreign_key => false          # don't create a constraint
 
-You can also modify the behavior using +:on_delete+, +:on_update+, and +:deferrable+
+    t.integer :author_id, :foreign_key => { :references => :authors }        # same as automatic behavior
+    t.integer :author,    :foreign_key => { :reference => :authors}          # same default name
+    t.integer :author_id, :foreign_key => { :references => [:authors, :id] } # same as automatic behavior
+    t.integer :author_id, :foreign_key => { :references => :people }         # override table name
+    t.integer :author_id, :foreign_key => { :references => [:people, :ssn] } # override table name and key
+    t.integer :author_id, :foreign_key => { :references => nil }             # don't create a constraint
+    t.integer :author_id, :foreign_key => { :name => "my_fk" }               # override default generated constraint name
+    t.integer :author_id, :foreign_key => { :on_delete => :cascade }
+    t.integer :author_id, :foreign_key => { :on_update: => :set_null }
+    t.integer :author_id, :foreign_key => { :deferrable => true }
 
-    t.integer :author_id, :on_delete => :cascade
+Of course the options can be combined, e.g.
 
-SchemaPlus also creates foreign keys when used rails' <tt>t.references</tt>
-or <tt>t.belongs_to</tt>< which take the singular of the referenced table
-name and implicitly create the column suffixed with +_id+, and it accepts
-the same arguments.
+    t.integer :author_id, :foreign_key => { :name => "my_fk", :on_delete => :no_action }
+
+As a shorthand, all options except +:name+ can be specified without placing them in a hash, e.g.
+
+    t.integer :author_id, :on_delete => :cascade
+    t.integer :author_id, :references => nil
 
 The foreign key behavior can be configured globally (see Config) or per-table (see create_table).
 
@@ -110,42 +161,62 @@ that reference a given table.  See SchemaPlus::ActiveRecord::ConnectionAdapters:
 
 === Views
 
-SchemaPlus provides support for creating and dropping views.  For example:
+SchemaPlus provides support for creating and dropping views.  In a migration, a view can be created using a rails relation or literal sql:
+
+  create_view :posts_commented_by_staff,  Post.joins(:comment => :user).where(:users => {:role => 'staff'}).uniq
+  create_view :uncommented_posts,        "SELECT * FROM posts LEFT OUTER JOIN comments ON comments.post_id = posts.id WHERE comments.id IS NULL"
+
+And can be dropped:
 
-  create_view :uncommented_posts, "SELECT * FROM posts LEFT OUTER JOIN comments ON comments.post_id = posts.id WHERE comments.id IS NULL"
+  drop_view :posts_commented_by_staff
   drop_view :uncommented_posts
 
-ActiveRecord works with views the same as with ordinary tables.  That is, for the above view you can define
+ActiveRecord works with views the same as with ordinary tables.  That is, for the above views you can define
 
-  class UncommentedPosts < ActiveRecord::Base
+  class PostCommentedByStaff < ActiveRecord::Base
+    table_name = "posts_commented_by_staff"
   end
 
-=== Column Defaults
+  class UncommentedPost < ActiveRecord::Base
+  end
+
+=== Column Defaults: Expressions
+
+SchemaPlus allows defaults to be set using expressions or constant values:
+
+  t.datetime :seen_at, :default => { :expr => 'NOW()' }
+  t.datetime :seen_at, :default => { :value => "2011-12-11 00:00:00" }
+
+Note that in MySQL only the TIMESTAMP column data type accepts SQL column
+defaults and Rails uses DATETIME, so expressions can't be used with MySQL.
 
-SchemaPlus allows expressions to be used as column defaults.  For example:
+The standard syntax will still work as usual:
+
+  t.datetime :seen_at, :default => "2011-12-11 00:00:00"
+
+Also, as a convenience
 
   t.datetime :seen_at, :default => :now
 
-resolves to
+resolves to:
 
-  DEFAULT NOW() # PostgreSQL
-  (DATETIME('now')) # SQLite3
-  invalid # MySQL
+  NOW()                 # PostgreSQL
+  (DATETIME('now'))     # SQLite3
+  invalid               # MySQL
 
-Arbitrary SQL expressions can also be specified by passing a hash with an :expr parameter:
+=== Column Defaults: Using
 
-  t.datetime :seen_at, :default => { :expr => 'NOW()' }
+SchemaPlus introduces a constant <tt>ActiveRecord::DB_DEFAULT</tt> that you can use to explicitly instruct the database to use the column default value (or expression).  For example:
 
-In MySQL only the TIMESTAMP column accepts SQL column defaults and Rails uses DATETIME,
-so this is not possible at this time.
+  Post.create(:category => ActiveRecord::DB_DEFAULT)
+  post.update_attributes(:category => ActiveRecord::DB_DEFAULT)
 
-Standard default values can be specified verbosely:
+(Without <tt>ActiveRecord::DB_DEFAULT</tt>, you can update a value to <tt>NULL</tt> but not to its default value.) 
 
-  t.datetime :seen_at, :default => { :value => "2011-12-11 00:00:00" }
+Note that after updating, you would need to reload a record to replace <tt>ActiveRecord::DB_DEFAULT</tt> with the value assigned by the database.
 
-But the standard syntax will still work as usual:
+Note also that Sqlite3 does not support <tt>ActiveRecord::DB_DEFAULT</tt>; attempting to use it will raise <tt>ActiveRecord::StatementInvalid</tt>
 
-  t.datetime :seen_at, :default => "2011-12-11 00:00:00"
 
 === Schema Dump and Load (schema.rb)
 
@@ -161,9 +232,9 @@ definition statements rather than relying on the auto-creation behavior,
 for maximum clarity and for independence from global config.  And
 correspondingly, when loading a schema, i.e. with the context of
 <tt>ActiveRecord::Schema.define</tt>, SchemaPlus ensures that auto creation of
-foreign keys is turned off regardless of the global setting.  But if for
+foreign key constraints is turned off regardless of the global setting.  But if for
 some reason you are creating your schema.rb file by hand, and would like to
-take advantage of auto-creation of foreign keys, you can re-enable it:
+take advantage of auto-creation of foreign key constraints, you can re-enable it:
 
     ActiveRecord::Schema.define do
         SchemaPlus.config.foreign_keys.auto_create = true
@@ -173,27 +244,58 @@ take advantage of auto-creation of foreign keys, you can re-enable it:
     end
 
 
-== History
+== Release notes:
+
+=== master (to be released)
+
+* No longer support rails < 3.2 and ruby < 1.9
+
+* New feature: specify foreign key constraints using :foreign_key => { ... }, motivated in particular to support :name (suggested by https://github.com/daniele-m)
+
+* New feature: create view using ActiveRecord relation
+
+* New feature: <tt>ActiveRecord::DB_DEFAULT</tt> (suggested by https://github.com/zaadjis)
+
+* New feature: renaming a table renames its indexes and constraints correspondingly.
+
+* Bug fix for postgres :kind index attribute (thanks to https://github.com/eugenebolshakov)
 
-* Recent Release notes:
-    * 0.4.1 - bug fix: don't attempt foreign key creation for t.belongs_to ... :polymorphic => true
-    * 0.4.0 - add :force for create_view (suggested by greglazarev[https://github.com/greglazarev]).  cleanups by betelgeuse[https://github.com/betelgeuse]
-    * 0.3.4 - bug fix: regression causing :default => false to be ignored
-    * 0.3.3 - bug fix: properly handle boolean defaults in mysql
-    * 0.3.2 - bug fix: make sure rake db:schema:load initializes schema_plus 
-    * 0.3.1 - bug fix for PostgreSQL schema dump after change_column_default(... nil)
-    * 0.3.0 - add :default => expressions (Thanks to Luke Saunders).  support rails 3.2 and ruby 1.9.3
-    * 0.2.1 - suppress duplicate add_indexes.  compatibility with rails 3.2.0.rc2
+* Sort fks in dump for stability (thanks to https://github.com/zephyr-dev)
+
+* Bug fix: change_column should maintain foreign key constraints even when config.foreign_keys.auto_create is false
+
+* Bug fix: quote default expressions in schema dump (thanks to https://github.com/jonleighton)
+
+* Bug fix: when removing a foreign key constraint, remove its auto-generated index.
+
+* Bug fix: SchemaDumper.ignore_tables needs to support regexps (suggeste by https://github.com/mtalcott)
+
+* Bug fix: More robust handling of Postgresql schema_search path (suggested by https://github.com/mtalcott)
+
+* Bug fix: Only get index, view, and foreign key information from current schema (thanks to https://github.com/bhavinkamani)
+
+=== Earlier releases
+* 0.4.1 - Bug fix: don't attempt foreign key creation for t.belongs_to ... :polymorphic => true
+* 0.4.0 - Add :force for create_view (suggested by greglazarev[https://github.com/greglazarev]).  cleanups by betelgeuse[https://github.com/betelgeuse]
+* 0.3.4 - Bug fix: regression causing :default => false to be ignored
+* 0.3.3 - Bug fix: properly handle boolean defaults in mysql
+* 0.3.2 - Bug fix: make sure rake db:schema:load initializes schema_plus 
+* 0.3.1 - Bug fix for PostgreSQL schema dump after change_column_default(... nil)
+* 0.3.0 - Add :default => expressions (Thanks to Luke Saunders).  support rails 3.2 and ruby 1.9.3
+* 0.2.1 - Suppress duplicate add_indexes.  compatibility with rails 3.2.0.rc2
+
+== History
 
 * SchemaPlus is derived from several "Red Hill On Rails" plugins
   originally created by harukizaemon (https://github.com/harukizaemon)
   with later contributions from 
   * Michał Łomnicki (https://github.com/mlomnicki)
+  * Ronen Barzel (https://github.com/ronen)
   * François Beausoleil (https://github.com/francois)
   * Greg Barnett (https://github.com/greg-barnett)
-  * Ronen Barzel (https://github.com/ronen)
   * Luke Saunders (https://github.com/lukesaunders)
 
+
 * SchemaPlus was created in 2011 by Michał Łomnicki and Ronen Barzel
 
 
@@ -203,28 +305,24 @@ take advantage of auto-creation of foreign keys, you can re-enable it:
 SchemaPlus is tested using rspec and rvm, with some hackery to test against
 multiple versions of rails and ruby and db adapters.  To run the tests,
 after you've forked & cloned: Make sure you have Postgresql and MySQL
-running.  Create database user "schema_plus" with permissions for database
-"schema_plus_unittest".  Then:
-
+running.  You'll need db users with permissions to create and access
+databases (schema_plus_test and schema_plus_test2).  Default user is
+'postgres' for Postgresql and 'schema_plus' for MySQL; you can change them via
+        $ export POSTGRES_DB_USER = pgusername
+        $ export MYSQL_DB_USER = mysqlusername
+Then:
   $ cd schema_plus
   $ bundle install
-  $ rake postgresql:build_databases
-  $ rake mysql:build_databases
-  $ ./runspecs --install  # do this once, it runs 'bundle install' for all versions (slow)
+  $ rake create_databases
+  $ ./runspecs --install  # do this once, it runs 'bundle install' for all versions
   $ ./runspecs # as many times as you like
 
-See <tt>./runspecs --help</tt> for more options.  You can also manually pick a specific version of rails and ruby to use, such as:
+See <tt>./runspecs --help</tt> for more options.  You can also manually pick a specific version of rails, ruby, and db to use, such as:
   $ rvm use 1.9.2
-  $ export BUNDLE_GEMFILE=gemfiles/Gemfile.rails-3.1
+  $ export BUNDLE_GEMFILE=gemfiles/rails-3.2/Gemfile.sqlite3
   $ bundle exec rake spec
 
-And you can run the specs for a specific adapter:
-  $ rake postgresql:spec # to run postgresql tests only
-  $ rake mysql:spec # to run mysql tests only
-  $ rake mysql2:spec # to run mysql2 tests only
-  $ rake sqlite3:spec # to run sqlite3 tests only
-
-If you're running ruby 1.9, code coverage results will be in coverage/index.html -- it should be at 100% coverage.
+Code coverage results will be in coverage/index.html -- it should be at 100% coverage if you're running against all databases
 
 == License
 

data/Rakefile

@@ -1,70 +1,81 @@
 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}"
-      spec.fail_on_error = false
-    end
-  end
-end
+task :default => :spec
 
-desc 'Run postgresql, mysql2 and sqlite3 tests'
-task :spec do 
-  %w[postgresql mysql mysql2 sqlite3].each do |adapter|
+desc 'Run test for adapter whose name is suffix of current Gemfile'
+task :spec do
+    gemfile = ENV['BUNDLE_GEMFILE']
+    fail "BUNDLE_GEMFILE environment variable not set" unless gemfile
+    adapter = File.extname(gemfile).sub(/^[.]/, '')
+    fail "BUNDLE_GEMFILE filename does not end with .db adapter name" if adapter.empty?
     Rake::Task["#{adapter}:spec"].invoke
-  end
 end
 
-task :default => :spec
-
-require 'rake/rdoctask'
+require 'rdoc/task'
 Rake::RDocTask.new do |rdoc|
-  version = File.exist?('VERSION') ? File.read('VERSION') : ""
+  require File.dirname(__FILE__) + '/lib/schema_plus/version'
 
   rdoc.rdoc_dir = 'rdoc'
-  rdoc.title = "schema_plus #{version}"
+  rdoc.title = "schema_plus #{SchemaPlus::VERSION}"
   rdoc.rdoc_files.include('README*')
   rdoc.rdoc_files.include('lib/**/*.rb')
 end
 
-namespace :postgresql do
-  desc 'Build the PostgreSQL test databases'
-  task :build_databases do
-    %x( createdb -E UTF8 schema_plus_unittest )
+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}"
+      spec.fail_on_error = true
+    end
   end
+end
 
-  desc 'Drop the PostgreSQL test databases'
-  task :drop_databases do
-    %x( dropdb schema_plus_unittest )
+DATABASES = %w[schema_plus_test]
+[ 
+  { namespace: :postgresql, uservar: 'POSTGRES_DB_USER', defaultuser: 'postgres', create: "createdb -U '%{user}' %{dbname}", drop: "dropdb -U '%{user}' %{dbname}" },
+  { namespace: :mysql, uservar: 'MYSQL_DB_USER', defaultuser: 'schema_plus', create: "mysqladmin -u '%{user}' create %{dbname}", drop: "mysqladmin -u '%{user}' -f drop %{dbname}" }
+].each do |db|
+  namespace db[:namespace] do
+    user = ENV.fetch db[:uservar], db[:defaultuser]
+    task :create_databases do
+      DATABASES.each do |dbname|
+        system(db[:create] % {user: user, dbname: dbname})
+      end
+    end
+    task :drop_databases do
+      DATABASES.each do |dbname|
+        system(db[:drop] % {user: user, dbname: dbname})
+      end
+    end
   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 = ENV.fetch('MYSQL_DB_USER', 'schema_plus')
-namespace :mysql do
-  desc 'Build the MySQL test databases'
-  task :build_databases do
-    %x( echo "create DATABASE schema_plus_unittest DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_unicode_ci " | mysql --user=#{MYSQL_DB_USER})
-  end
+desc 'Run postgresql, mysql, mysql2 and sqlite3 tests'
+task :specs do 
+  invoke_multiple(%w[postgresql mysql mysql2 sqlite3], "spec")
+end
 
-  desc 'Drop the MySQL test databases' 
-  task :drop_databases do
-    %x( mysqladmin --user=#{MYSQL_DB_USER} -f drop schema_plus_unittest )
-  end
+desc 'Create test databases'
+task :create_databases do
+  invoke_multiple(%w[postgresql mysql], "create_databases")
+end
 
-  desc 'Rebuild the MySQL test databases'
-  task :rebuild_databases => [:drop_databases, :build_databases]
+desc 'Drop test databases'
+task :drop_databases do
+  invoke_multiple(%w[postgresql mysql], "drop_databases")
 end
 
-task :build_mysql_databases => 'mysql:build_databases'
-task :drop_mysql_databases => 'mysql:drop_databases'
-task :rebuild_mysql_databases => 'mysql:rebuild_databases'
+def invoke_multiple(namespaces, task)
+  failed = namespaces.reject { |adapter|
+    begin
+      Rake::Task["#{adapter}:#{task}"].invoke
+      true
+    rescue => e
+      warn "\n#{e}\n"
+      false
+    end
+  }
+  fail "Failure in: #{failed.join(', ')}" if failed.any?
+end