schema_plus 1.0.1 → 1.1.0

data/spec/schema_spec.rb

@@ -36,7 +36,6 @@ describe ActiveRecord::Schema do
   protected
   def do_schema
     define_schema do
-      connection.tables.each do |table| drop_table table end
 
       create_table :users, :force => true do
       end

data/spec/spec_helper.rb

@@ -38,7 +38,7 @@ def define_schema(config={}, &block)
     ActiveRecord::Migration.suppress_messages do
       ActiveRecord::Schema.define do
         connection.tables.each do |table|
-          drop_table table
+          drop_table table, :cascade => true
         end
         instance_eval &block
       end

data/spec/support/matchers/reference.rb

@@ -22,6 +22,7 @@ module SchemaPlusMatchers
       @result.keep_if {|fk| fk.column_names == @column_names } if @column_names
       @result.keep_if {|fk| fk.on_update == @on_update } if @on_update
       @result.keep_if {|fk| fk.on_delete == @on_delete } if @on_delete
+      @result.keep_if {|fk| fk.deferrable == @deferrable } if @deferrable
       @result.keep_if {|fk| fk.name == @name } if @name
       !@result.empty?
     end
@@ -34,6 +35,7 @@ module SchemaPlusMatchers
       with = []
       with << "on_update=#{@on_update.inspect}" if @on_update
       with << "on_delete=#{@on_delete.inspect}" if @on_delete
+      with << "deferrable=#{@deferrable.inspect}" if @deferrable
       with << "name=#{@name.inspect}" if @name
       msg += " with #{with.join(" and ")}" if with.any?
       msg
@@ -53,6 +55,11 @@ module SchemaPlusMatchers
       self
     end
 
+    def deferrable(action)
+      @deferrable = action
+      self
+    end
+
     def on_delete(action)
       @on_delete = action
       self

data/spec/views_spec.rb

@@ -130,7 +130,7 @@ describe ActiveRecord do
   def define_schema_and_data
     migration.suppress_messages do
       connection.views.each do |view| connection.drop_view view end
-      connection.tables.each do |table| connection.drop_table table end
+      connection.tables.each do |table| connection.drop_table table, cascade: true end
 
       schema.define do
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: schema_plus
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.1.0
   prerelease: 
 platform: ruby
 authors:
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-02-04 00:00:00.000000000 Z
+date: 2013-03-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -122,7 +122,7 @@ files:
 - .travis.yml
 - Gemfile
 - MIT-LICENSE
-- README.rdoc
+- README.md
 - Rakefile
 - gemfiles/rails-3.2/Gemfile.base
 - gemfiles/rails-3.2/Gemfile.mysql
@@ -163,7 +163,7 @@ files:
 - spec/index_definition_spec.rb
 - spec/index_spec.rb
 - spec/migration_spec.rb
-- spec/multiple_schemas_spec.rb
+- spec/named_schemas_spec.rb
 - spec/schema/auto_schema.rb
 - spec/schema/core_schema.rb
 - spec/schema_dumper_spec.rb
@@ -194,7 +194,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 1266061864634900724
+      hash: 1918846716163571609
 requirements: []
 rubyforge_project: schema_plus
 rubygems_version: 1.8.24
@@ -215,7 +215,7 @@ test_files:
 - spec/index_definition_spec.rb
 - spec/index_spec.rb
 - spec/migration_spec.rb
-- spec/multiple_schemas_spec.rb
+- spec/named_schemas_spec.rb
 - spec/schema/auto_schema.rb
 - spec/schema/core_schema.rb
 - spec/schema_dumper_spec.rb

data/README.rdoc

@@ -1,347 +0,0 @@
-= SchemaPlus
-
-
-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.
-
-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 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
-
-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
-
-Install from http://rubygems.org via
-
-        $ gem install "schema_plus"
-
-or in a Gemfile
-
-        gem "schema_plus"
-
-== Features
-
-Here some examples that show off the high points.  For full details see the
-{RDoc documentation}[http://rubydoc.info/gems/schema_plus].
-
-=== Indexes
-
-With standard rails migrations, you specify indexes separately from the table definition:
-
-    # Standard Rails approach...
-    create_table :parts do |t|
-      t.string :name
-      t.string :product_code
-    end
-
-    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, with options as desired
-
-    # More DRY way...
-    create_table :parts do |t|
-      t.string :name,           index: true
-      t.string :product_code,   index: { unique: true }
-    end
-
-The options hash can include an index name:
-
-    t.string :product_code,     index: { unique: true, name: "my_index_name" }
-
-You can also create multi-column indexes, for example:
-
-    t.string :first_name
-    t.string :last_name,        index: { with: :first_name }
-
-    t.string :country_code
-    t.string :area_code
-    t.string :local_number      index: { with: [:country_code, :area_code], unique: true }
-
-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.
-
-
-=== Foreign Key Constraints
-
-SchemaPlus adds support for foreign key constraints. In fact, for the
-common convention that you name a column with suffix +_id+ to indicate that
-it's a foreign key, SchemaPlus automatically defines the appropriate
-constraint.
-
-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_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
-
-    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 }
-
-Of course the options can be combined, e.g.
-
-    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).
-
-To examine your foreign key constraints, <tt>connection.foreign_keys</tt> returns a
-list of foreign key constraints defined for a given table, and
-<tt>connection.reverse_foreign_keys</tt> returns a list of foreign key constraints
-that reference a given table.  See SchemaPlus::ActiveRecord::ConnectionAdapters::ForeignKeyDefinition.
-
-=== Views
-
-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:
-
-  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 views you can define
-
-  class PostCommentedByStaff < ActiveRecord::Base
-    table_name = "posts_commented_by_staff"
-  end
-
-  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.
-
-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:
-
-  NOW()                 # PostgreSQL
-  (DATETIME('now'))     # SQLite3
-  invalid               # MySQL
-
-=== Column Defaults: Using
-
-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:
-
-  Post.create(category: ActiveRecord::DB_DEFAULT)
-  post.update_attributes(category: ActiveRecord::DB_DEFAULT)
-
-(Without <tt>ActiveRecord::DB_DEFAULT</tt>, you can update a value to <tt>NULL</tt> but not to its default value.) 
-
-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.
-
-Note also that Sqlite3 does not support <tt>ActiveRecord::DB_DEFAULT</tt>; attempting to use it will raise <tt>ActiveRecord::StatementInvalid</tt>
-
-
-=== Schema Dump and Load (schema.rb)
-
-When dumping <tt>schema.rb</tt>, SchemaPlus orders the views and tables in
-the schema dump alphabetically, but subject to the requirement that each
-table or view be defined before those that depend on it.  This allows all
-foreign key constraints to be defined within the scope of the table
-definition. (Unless there are cyclical dependencies, in which case some
-foreign keys constraints must be defined later.)
-
-Also, when dumping <tt>schema.rb</tt>, SchemaPlus dumps explicit foreign key
-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 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 key constraints, you can re-enable it:
-
-    ActiveRecord::Schema.define do
-        SchemaPlus.config.foreign_keys.auto_create = true
-        SchemaPlus.config.foreign_keys.auto_index = true
-
-        create_table ...etc...
-    end
-
-
-== Release notes:
-
-
-=== 1.0.1
-
-* README cleanups (thanks to https://github.com/denispeplin)
-
-* Now raises ArgumentError if index has both :case_sensitive => false and an :expression
-
-* Now creates consistent default name for foreign key constraints
-
-* Bug fix: respect :length keyword for index (thanks to https://github.com/teleological )
-
-* Bug fix: renaming table with multiple foreign key constraints (thanks to https://github.com/teleological )
-
-* Bug fix: don't dump :case_sensitive => false for index with an expression that includes "lower(name)".
-
-* Bug fix: Properly dump multi-column case-insensitive indexes
-
-=== 1.0.0
-
-* 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)
-
-* 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 (suggested 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)
-  * Luke Saunders (https://github.com/lukesaunders)
-
-
-* SchemaPlus was created in 2011 by Michał Łomnicki and Ronen Barzel
-
-
-
-== Testing
-
-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.  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 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.  In particular, to run
-rspec on a specific file or example (rather than running the full suite)
-you can do, e.g.
-
-  $ ./runspecs [other options] --rspec -- spec/migration_spec.rb -e 'default name'
-
-Code coverage results will be in coverage/index.html -- it should be at 100% coverage if you're running against all databases
-
-== License
-
-This gem is released under the MIT license.