time_range_uniqueness 1.0.0 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 868b4a177acdae3b835b05cb3b7d18741298b99592cdfb429dd38196287dc9f4
-  data.tar.gz: 3b2a570fe65b0a08024bd730e1743a15966d0c9bfd2c674d5533e70014a27d69
+  metadata.gz: dc737c44b6dbbf13c6781eef86f089832aaf04cda0a50c0d513f91e19536f600
+  data.tar.gz: 1be53b987bdc21f730b2ace9ea9aa9478eef92387ecdc6508a6bfad68f90d4ac
 SHA512:
-  metadata.gz: 8c01bcca608fc1341a154f3f7b40293f483ca27814fdfac96139edf390eac43b3d791c2b1aa8d9004d17597a91db06bfdd6205030c46d114abdddb2fd441d5ac
-  data.tar.gz: 5b31ad1001851747cb211231329bdab526750558482d152eaa4fbe4217ef7afc637287d14a6235f1d5d6b8dbdee85ce2286f6dd1babf1bdaa37cb01c29f5e8e5
+  metadata.gz: d6d32eb4c17f95d7d0815e692f09eed56d62aeb259a9c3b05e70fa2c78dfc59ac89fbd8127dc9bf33e29e8a5c5d2382ae21fdf07dd6ae906d9b36be3a878c4e5
+  data.tar.gz: 889b032899cbdc7cc3fc2cb73d05b593d438ecf112561dca2926a715c713d26cf92e5224cc85a9470b55c3404426484a5c66633ad8e716f7a13365e17c910bda

data/CHANGELOG.md

@@ -1,5 +1,23 @@
 ## [Unreleased]
 
+## [1.0.2] - 2026-05-31
+
+- Update the README to match the current behavior: document the Ruby >= 3.2 and
+  ActiveRecord >= 7.1 requirements, correct the migration example's version stamp, clarify
+  that `validates_time_range_uniqueness` is available on all models, and list the
+  validation/constraint behavior added in 1.0.0 and 1.0.1.
+
+## [1.0.1] - 2026-05-31
+
+- Fix the overlap validation to treat a `NULL` scope value as never-conflicting, matching
+  the exclusion constraint (`NULL = NULL` is never true in PostgreSQL). Previously the
+  validation reported a false overlap for rows the database would accept.
+- Support models with a composite primary key in the overlap validation. Previously the
+  validation raised `ArgumentError` when excluding the current record, so such models
+  could not be validated or created.
+- Raise `ArgumentError` when a custom `:name` exceeds PostgreSQL's 63-character identifier
+  limit, instead of relying on the database to truncate it silently.
+
 ## [1.0.0] - 2026-05-31
 
 - Require Ruby >= 3.2 and support ActiveRecord 7.1 through 8.x (and pg >= 1.5).

data/README.md

@@ -11,6 +11,17 @@ It adds support for creating exclusion constraints on PostgreSQL `tstzrange` col
 - **Migration Additions**: Adds a custom method for generating exclusion constraints on time range columns in PostgreSQL using `tstzrange`.
 - **Model Additions**: Adds validation to ensure time ranges do not overlap with existing records.
 - Supports optional scoping to ensure time ranges are unique within specified contexts (e.g., unique per event name).
+- Honors the time range's bound inclusivity (`..` vs `...`) so the model validation agrees with the database-level exclusion constraint.
+- Treats a `NULL` scope value as never-conflicting, matching PostgreSQL's exclusion-constraint semantics (`NULL = NULL` is never true).
+- Works with models that use a composite primary key.
+- Keeps generated constraint names within PostgreSQL's 63-character identifier limit, and raises if a custom `:name` exceeds it.
+- Quotes table and column identifiers in the generated migration and validation SQL.
+
+## Requirements
+
+- Ruby >= 3.2
+- ActiveRecord >= 7.1, < 9.0
+- PostgreSQL with the `btree_gist` extension available
 
 ## Installation
 
@@ -46,7 +57,7 @@ In your migrations, you can use the `add_time_range_uniqueness` method to add a
 ### Example
 
 ```ruby
-class AddEventTimeRangeUniqueness < ActiveRecord::Migration[6.1]
+class AddEventTimeRangeUniqueness < ActiveRecord::Migration[7.1]
   def change
     add_time_range_uniqueness :events,
                               with: :event_time_range,
@@ -60,7 +71,7 @@ This example ensures that the `event_time_range` column in the `events` table is
 
 ### Model Additions
 
-The gem also provides model-level validation to ensure time ranges do not overlap. You can include this validation in your models like this:
+The gem also provides model-level validation to ensure time ranges do not overlap. The `validates_time_range_uniqueness` class method is available on all ActiveRecord models, so you can declare it directly in your model like this:
 
 #### Options:
 - `with`: **(Required)** The name of the time range column to validate.

data/lib/time_range_uniqueness/migration_additions.rb

@@ -47,7 +47,7 @@ module TimeRangeUniqueness
     # @option options [Array<Symbol>] :scope (Optional) Columns to scope the uniqueness check.
     # @option options [String] :name (Optional) The name of the constraint.
     def add_time_range_uniqueness(table, options = {})
-      raise ArgumentError, 'You must specify the :with option with the time range column name' unless options[:with]
+      validate_options!(options)
 
       time_range_column = options[:with]
       scope_columns = Array(options[:scope])
@@ -61,6 +61,19 @@ module TimeRangeUniqueness
 
     private
 
+    # Validates the options passed to +add_time_range_uniqueness+.
+    #
+    # @param options [Hash] The options for the constraint.
+    # @raise [ArgumentError] If +:with+ is missing or +:name+ exceeds the identifier limit.
+    def validate_options!(options)
+      raise ArgumentError, 'You must specify the :with option with the time range column name' unless options[:with]
+
+      name = options[:name]
+      return unless name && name.to_s.length > MAX_IDENTIFIER_LENGTH
+
+      raise ArgumentError, "The :name option exceeds the #{MAX_IDENTIFIER_LENGTH}-character identifier limit"
+    end
+
     # Applies the changes for the up migration.
     #
     # @param table [Symbol, String] The name of the table.

data/lib/time_range_uniqueness/model_additions.rb

@@ -70,15 +70,16 @@ module TimeRangeUniqueness
       time_range = record.public_send(time_range_column)
       return false if time_range.nil?
 
+      # A NULL scope value can never satisfy the exclusion constraint's `=` comparison,
+      # so such a record can never conflict at the database level. Mirror that here.
+      return false if scope_columns.any? { |col| record.public_send(col).nil? }
+
       column = record.class.connection.quote_column_name(time_range_column)
       bounds = time_range.exclude_end? ? '[)' : '[]'
 
-      scoped_relation(record, scope_columns).where(
-        "#{column} && tstzrange(?, ?, ?)",
-        time_range.begin,
-        time_range.end,
-        bounds
-      ).exists?
+      scoped_relation(record, scope_columns)
+        .where("#{column} && tstzrange(?, ?, ?)", time_range.begin, time_range.end, bounds)
+        .exists?
     end
 
     # Builds the set of other records to check against, optionally scoped by the given columns.
@@ -88,7 +89,10 @@ module TimeRangeUniqueness
     # @return [ActiveRecord::Relation] All other records, scoped by the given columns.
     def self.scoped_relation(record, scope_columns)
       klass = record.class
-      relation = klass.where.not(klass.primary_key => record.id)
+      # Pair each primary key column with its value so this works for both single
+      # and composite primary keys (record.id is an array for composite keys).
+      excluded = Array(klass.primary_key).zip(Array(record.id)).to_h
+      relation = klass.where.not(excluded)
 
       scope_columns.each do |col|
         relation = relation.where(col => record.public_send(col))

data/lib/time_range_uniqueness/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module TimeRangeUniqueness
-  VERSION = '1.0.0'
+  VERSION = '1.0.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: time_range_uniqueness
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.2
 platform: ruby
 authors:
 - j-boers-13
@@ -71,7 +71,7 @@ licenses:
 metadata:
   source_code_uri: https://github.com/j-boers-13/time_range_uniqueness
   homepage_uri: https://github.com/j-boers-13/time_range_uniqueness
-  changelog_uri: https://github.com/j-boers-13/time_range_uniqueness/CHANGELOG.md
+  changelog_uri: https://github.com/j-boers-13/time_range_uniqueness/blob/main/CHANGELOG.md
   rubygems_mfa_required: 'true'
 rdoc_options: []
 require_paths: