rein 4.0.0 → 5.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 24623f32cadd63604381d8dad8884880eae0bd4b14e9cbe9b374e35f95bf75a1
-  data.tar.gz: b6dcaf5464e761520a435e4bc16c6a4476b229dd9bccae99e135931ed169acdd
+  metadata.gz: 12dbfe85b21d4fe3a16982a86d784701a74ed611046b9eaa0dcddea86afb8bd3
+  data.tar.gz: be0b34a4ecaa0098217e6bb8327fbc1cf09adf329a3ceb30d26afb4be3fb071b
 SHA512:
-  metadata.gz: ff7356d2879f6e6a485d2978fdef2dafe2eb0e3e26e1ea1574dda769b0e1026f474c34f1d141ecb1ae92e2736de7348544df70fdc11445c3c39895e4b7b1aaf1
-  data.tar.gz: f0ce01bb2a2033370962318d8a49719763df2b5b1fbc46ffe381ba582a294a58c7dcb610bb766ca8213d70ea4f29ff06e9d479691a65f537a598e4ffff59a1f7
+  metadata.gz: a9bce885142492aa55ef15346ef19d1d631a1f85cd9ba8bc7c60ce977bd481a3d2962c3507bccde0ed9c5306f8a8f6d76b30e8e83a721f030f04df999a03ac47
+  data.tar.gz: 9e8c8ef912098fc12d944c1198783bf2b0308fa3a241ca937ae03d4ee9532c9acd391da045bb778a002c2cf528c81112008309614254aaf01a1f1863e9385add

data/CHANGELOG.md

@@ -1,3 +1,9 @@
+## 5.0.0 (2019-08-23)
+
+* Upgrade development deps
+* Add support for ActiveRecord 6
+* Add `where` option to exclusion constraints
+
 ## 4.0.0 (2019-01-28)
 
 * Add exclusion constraints

data/README.md

@@ -1,6 +1,6 @@
 # Rein
 
-[![Build Status](https://travis-ci.org/nullobject/rein.svg?branch=master)](https://travis-ci.org/nullobject/rein)
+[![Build Status](https://travis-ci.com/nullobject/rein.svg?branch=master)](https://travis-ci.com/nullobject/rein)
 
 [Data integrity](http://en.wikipedia.org/wiki/Data_integrity) is a good thing.
 Constraining the values allowed by your application at the database-level,
@@ -164,13 +164,15 @@ add_unique_constraint :authors, :name, deferrable: false
 ### Exclusion Constraints
 
 An exclusion constraint is a lot like a unique constraint, but more general.
-Whereas a unique constraint forbids two rows from having all constrained columns be *equal*,
-an exclusion constraint forbids two rows from having all constrained columns be *some relationship*,
-where the relationship is up to you (and can be different for each column).
-For instance you can prevent two ranges from overlapping with the `&&` operator.
-You can read more in 
-[the Postgres docs](https://www.postgresql.org/docs/9.0/static/ddl-constraints.html#DDL-CONSTRAINTS-EXCLUSION)
-or [a slideshow by the author, Jeff Davis](https://www.slideshare.net/pgconf/not-just-unique-exclusion-constraints).
+Whereas a unique constraint forbids two rows from having all constrained
+columns be *equal*, an exclusion constraint forbids two rows from having all
+constrained columns be *some relationship*, where the relationship is up to you
+(and can be different for each column).  For instance you can prevent two
+ranges from overlapping with the `&&` operator.  You can read more in [the
+Postgres
+docs](https://www.postgresql.org/docs/9.0/static/ddl-constraints.html#DDL-CONSTRAINTS-EXCLUSION)
+or [a slideshow by the author, Jeff
+Davis](https://www.slideshare.net/pgconf/not-just-unique-exclusion-constraints).
 
 For example, no two people should own copyright to a book at the same time:
 
@@ -178,14 +180,14 @@ For example, no two people should own copyright to a book at the same time:
 add_exclusion_constraint :book_owners, [[:book_id, '='], [:owned_during, '&&']], using: :gist
 ```
 
-By default, the database checks exclusion constraints immediately (i.e. as soon as
-a record is created or updated). If a record with an excluded value exists,
+By default, the database checks exclusion constraints immediately (i.e. as soon
+as a record is created or updated). If a record with an excluded value exists,
 then the database will raise an error.
 
 Sometimes it is necessary to wait until the end of a transaction to do the
-checking (e.g. maybe you want to move the date a copyright changed hands). To do so, you
-need to tell the database to *defer* checking the constraint until the end of
-the current transaction:
+checking (e.g. maybe you want to move the date a copyright changed hands). To
+do so, you need to tell the database to *defer* checking the constraint until
+the end of the current transaction:
 
 ```sql
 BEGIN;
@@ -213,6 +215,21 @@ a transaction, then you can set the `deferrable` option to `false`:
 add_exclusion_constraint :book_owners, [[:book_id, '='], [:owned_during, '&&']], using: :gist, deferrable: false
 ```
 
+If you want to specify something like a operator class for a attribute specific
+attribute, you can add it to the attribute specification between attribute name
+and the operator:
+
+```ruby
+add_exclusion_constraint :book_owners, [[:book_id, :gist_int8_ops, '='], [:owned_during, '&&']], using: :gist
+```
+
+If you want to set the constraint to a subset of the table, you can use a `where`
+option to set the filter condition:
+
+```ruby
+add_exclusion_constraint :books, [[:isbn, '=']], using: :gist, where: "state='active'"
+```
+
 ### Inclusion Constraints
 
 An inclusion constraint specifies the possible values that a column value can

data/lib/rein/constraint/exclusion.rb

@@ -42,15 +42,24 @@ module Rein
         name = Util.constraint_name(table, attributes.map { |att| att[0] }.join('_'), 'exclude', options)
         table = Util.wrap_identifier(table)
         attributes = attributes.map do |attribute|
-          "#{Util.wrap_identifier(attribute[0])} WITH #{attribute[1]}"
+          _get_attribute_expression(attribute)
         end
         initially = options[:deferred] ? 'DEFERRED' : 'IMMEDIATE'
         using = options[:using] ? " USING #{options[:using]}" : ''
         sql = "ALTER TABLE #{table} ADD CONSTRAINT #{name} EXCLUDE#{using} (#{attributes.join(', ')})"
+        sql << " WHERE (#{options[:where]})" if options[:where].present?
         sql << " DEFERRABLE INITIALLY #{initially}" unless options[:deferrable] == false
         execute(sql)
       end
 
+      def _get_attribute_expression(attribute)
+        if attribute.size > 2
+          "#{Util.wrap_identifier(attribute[0])} #{attribute[1, attribute.size - 2].join(' ')} WITH #{attribute.last}"
+        else
+          "#{Util.wrap_identifier(attribute[0])} WITH #{attribute[1]}"
+        end
+      end
+
       def _remove_exclusion_constraint(table, attributes, options = {})
         name = Util.constraint_name(table, attributes.map { |att| att[0] }.join('_'), 'exclude', options)
         table = Util.wrap_identifier(table)

data/lib/rein/version.rb

@@ -1,3 +1,3 @@
 module Rein
-  VERSION = '4.0.0'.freeze
+  VERSION = '5.0.0'.freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rein
 version: !ruby/object:Gem::Version
-  version: 4.0.0
+  version: 5.0.0
 platform: ruby
 authors:
 - Joshua Bassett
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-01-28 00:00:00.000000000 Z
+date: 2019-08-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -17,9 +17,6 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 4.0.0
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '6'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -27,9 +24,6 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 4.0.0
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '6'
 - !ruby/object:Gem::Dependency
   name: activesupport
   requirement: !ruby/object:Gem::Requirement
@@ -37,9 +31,6 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 4.0.0
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '6'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -47,9 +38,6 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 4.0.0
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '6'
 - !ruby/object:Gem::Dependency
   name: appraisal
   requirement: !ruby/object:Gem::Requirement
@@ -126,14 +114,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.63.1
+        version: 0.67.2
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.63.1
+        version: 0.67.2
 description: Rein adds bunch of methods to your ActiveRecord migrations so you can
   easily tame your database.
 email: josh.bassett@gmail.com
@@ -180,7 +168,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.0
+rubyforge_project: 
+rubygems_version: 2.7.6.2
 signing_key: 
 specification_version: 4
 summary: Database constraints made easy for ActiveRecord.