rails-uuid-pk 0.12.0 → 0.13.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0ef202d7fd8ed44687383011c2306cdafc16fc9a05505270c270a753d4fd4a33
-  data.tar.gz: fd9416e86ae299c7d693fcba9bc0e71d179940cd4e1e29dbd4bfc892e30e0248
+  metadata.gz: 46d317c27d7ed27fb503bba3020d93e48f770e2492c8561c347544c9e8d4db4f
+  data.tar.gz: 39ed2abf06c8424ae2e431ee5cd09e20849a475c671266e6be7345768473bffd
 SHA512:
-  metadata.gz: 4f675cb556f985b0060cc34297182d5dbe1860a05cce42ce1b8de62e4b5f4ea89b07ae84669615dbb109d6f4c4bc0779c6a90bcaf9b0af3cc1b8d42b8588f8cc
-  data.tar.gz: 9ac0c2032a0036bc9a5a7441391f30b3991c0557446605ac1bb9b35a100e8fdb9cad565443536ef4b833f3c7c0793ff085b51996e1d75a5e018472ff4edd92af
+  metadata.gz: eca0cdf854a9924f4268d3cf33d8c9b4c13061d569e9551e6ceb591873f406e5c451daccc26206b44ebcacd054a4ea4a7d486a32596790fd61a0ef61b5dd0380
+  data.tar.gz: 10852d080506a8305adf8c2c538a788d9f6790c2dec4770a7329f8cb2acaf95e66d2903daf8b69ac0753d6f16ec5c9e1d478e9841cc73088227b6f710711580f

data/ARCHITECTURE.md

@@ -0,0 +1,508 @@
+# Architecture Overview
+
+This document outlines the architectural decisions, design principles, and technical trade-offs made in rails-uuid-pk. It serves as a guide for understanding why certain approaches were chosen and the implications of those decisions.
+
+## Core Design Principles
+
+### Zero-Configuration Philosophy
+**Decision**: Automatic UUIDv7 primary keys for all models by default
+- **Rationale**: Maximize ease of adoption for Rails developers while modernizing primary key usage
+- **Implementation**: Railtie-based automatic inclusion in `ActiveRecord::Base` with opt-out mechanism
+- **Impact**: Just add the gem to Gemfile - all models use UUIDv7 PKs, exceptions require explicit opt-out
+
+### Database Agnosticism
+**Decision**: Support PostgreSQL, MySQL, and SQLite with unified API
+- **Rationale**: Enable database portability and CI/testing flexibility
+- **Implementation**: Adapter-specific extensions with common interface
+- **Impact**: Developers can switch databases without code changes
+
+### App-Level UUID Generation
+**Decision**: Generate UUIDs in application code, not database
+- **Rationale**: Maximum compatibility across database versions and types
+- **Implementation**: `before_create` callback using `SecureRandom.uuid_v7`
+- **Trade-offs**: No database-native UUID functions, but universal compatibility
+
+## Architectural Components
+
+### 1. Core Modules
+
+#### Concern (`lib/rails_uuid_pk/concern.rb`)
+```ruby
+module RailsUuidPk
+  module HasUuidv7PrimaryKey
+    extend ActiveSupport::Concern
+
+    included do
+      before_create :assign_uuidv7_if_needed, if: -> { id.nil? }
+    end
+
+    private
+
+    def assign_uuidv7_if_needed
+      # Skip if id was already set (manual set, bulk insert with ids, etc)
+      return if id.present?
+
+      uuid = SecureRandom.uuid_v7
+      RailsUuidPk.log(:debug, "Assigned UUIDv7 #{uuid} to #{self.class.name}")
+      self.id = uuid
+    end
+  end
+end
+```
+
+**Responsibilities**:
+- UUIDv7 generation logic
+- Defensive programming (only assign if id is nil)
+- Hook into ActiveRecord lifecycle
+
+#### Migration Helpers (`lib/rails_uuid_pk/migration_helpers.rb`)
+**Responsibilities**:
+- Automatic foreign key type detection
+- Polymorphic association support
+- Schema inspection and caching
+
+#### Custom Type (`lib/rails_uuid_pk/type.rb`)
+**Responsibilities**:
+- UUID validation and casting
+- Schema dumping compatibility
+- Rails version awareness
+
+#### Railtie (`lib/rails_uuid_pk/railtie.rb`)
+**Responsibilities**:
+- Automatic gem integration
+- Database adapter extensions
+- Generator configuration
+
+#### Logging Framework (`lib/rails_uuid_pk.rb`)
+**Responsibilities**:
+- Structured logging infrastructure
+- Rails logger integration with fallback
+- Debug logging for UUID assignment, migration helpers, and adapter registration
+- Production observability support
+- Structured logging with `[RailsUuidPk]` prefix for easy filtering
+- Compatible with existing Rails logging and monitoring systems (Datadog, CloudWatch, etc.)
+
+### 2. Database Adapter Extensions
+
+#### PostgreSQL (Native Support)
+- Uses PostgreSQL's native UUID type support (16 bytes)
+- No adapter extension needed - Rails handles UUID types natively
+- Full database function compatibility
+- Optimized for PostgreSQL 18's enhanced UUID handling
+
+#### Shared UUID Adapter Extension
+```ruby
+# lib/rails_uuid_pk/uuid_adapter_extension.rb
+module RailsUuidPk
+  module UuidAdapterExtension
+    # Common UUID type support methods shared by MySQL and SQLite adapters
+    def native_database_types
+      super.merge(uuid: { name: "varchar", limit: 36 })
+    end
+
+    def valid_type?(type)
+      return true if type == :uuid
+      super
+    end
+
+    def register_uuid_types(m = type_map)
+      RailsUuidPk.log(:debug, "Registering UUID types on #{m.class}")
+      m.register_type(/varchar\(36\)/i) { RailsUuidPk::Type::Uuid.new }
+      m.register_type("uuid") { RailsUuidPk::Type::Uuid.new }
+    end
+
+    def initialize_type_map(m = type_map)
+      super
+      register_uuid_types(m)
+    end
+
+    def configure_connection
+      super
+      register_uuid_types
+    end
+
+    def type_to_dump(column)
+      if column.type == :uuid
+        return [ :uuid, {} ]
+      end
+      super
+    end
+  end
+end
+```
+
+#### MySQL (`mysql2` gem integration)
+```ruby
+# lib/rails_uuid_pk/mysql2_adapter_extension.rb
+module RailsUuidPk
+  module Mysql2AdapterExtension
+    include UuidAdapterExtension
+
+    # MySQL-specific connection configuration
+    def configure_connection
+      super  # Standard UUID type registration
+    end
+  end
+end
+```
+
+#### SQLite (`sqlite3` gem integration)
+```ruby
+# lib/rails_uuid_pk/sqlite3_adapter_extension.rb
+module RailsUuidPk
+  module Sqlite3AdapterExtension
+    include UuidAdapterExtension
+
+    # SQLite-specific connection configuration with transaction awareness
+    def configure_connection
+      # Only call super if not inside a transaction, as PRAGMA statements
+      # cannot be executed inside transactions in SQLite
+      super unless open_transactions > 0
+    end
+  end
+end
+```
+
+## Key Architectural Decisions
+
+### Decision 1: App-Level vs Database-Level Generation
+
+#### Chosen Approach: App-Level Generation
+```ruby
+# In application code
+before_create :assign_uuidv7_if_needed, if: -> { id.nil? }
+
+def assign_uuidv7_if_needed
+  return if id.present?
+  self.id = SecureRandom.uuid_v7
+end
+```
+
+#### Alternative Considered: Database-Level Generation
+```sql
+-- PostgreSQL native approach
+CREATE TABLE users (
+  id UUID PRIMARY KEY DEFAULT uuid_generate_v7(),
+  name VARCHAR(255)
+);
+```
+
+#### Trade-off Analysis
+
+| Aspect | App-Level | Database-Level |
+|--------|-----------|----------------|
+| **Compatibility** | Universal (all DBs) | DB-specific functions required |
+| **Performance** | Minimal overhead | Potentially faster (no app round-trip) |
+| **Testing** | Consistent across environments | Requires DB function setup |
+| **Migration** | App manages UUIDs | DB manages UUIDs |
+| **Dependencies** | Ruby SecureRandom only | Database extensions/functions |
+| **Consistency** | Guaranteed across transactions | Dependent on DB implementation |
+
+#### Rationale for App-Level Choice
+1. **Universal Compatibility**: Works with any database without extensions
+2. **Testing Simplicity**: Same behavior in development, test, and production
+3. **Migration Safety**: UUIDs are assigned before database constraints
+4. **Zero Dependencies**: No database-specific setup or extensions required
+5. **Performance**: `SecureRandom.uuid_v7` is sufficiently fast for most applications
+
+#### Bulk Operations Limitation
+The app-level callback approach has one important limitation: bulk operations bypass ActiveRecord callbacks. This means operations like `Model.import` or `Model.insert_all` won't automatically generate UUIDs. Applications requiring bulk imports must explicitly assign UUIDs:
+
+```ruby
+# Manual UUID assignment required for bulk operations
+users = [{ name: "Alice", id: SecureRandom.uuid_v7 }, { name: "Bob", id: SecureRandom.uuid_v7 }]
+User.insert_all(users) # Bypasses callbacks, requires explicit IDs
+```
+
+This is a conscious trade-off for universal compatibility and zero-configuration benefits.
+
+### Decision 2: UUIDv7 vs Other UUID Versions
+
+#### Chosen: UUIDv7 (RFC 9562)
+- **Monotonic Ordering**: Time-based ordering reduces index fragmentation
+- **Cryptographically Secure**: Uses system CSPRNG for randomness
+- **Standard Compliant**: Latest UUID standard with time-based ordering
+- **Database Friendly**: Better index locality than random UUIDs
+
+#### Alternatives Considered
+- **UUIDv4**: Random, maximum unpredictability, poor index performance
+- **UUIDv1**: MAC address based, privacy concerns, time-ordered
+- **Sequential IDs**: Auto-increment, predictable, good performance but security issues
+
+#### UUIDv7 Advantages for Rails Applications
+1. **Index Performance**: Monotonic ordering improves B-tree efficiency
+2. **Audit Capabilities**: Time-based ordering enables temporal queries
+3. **Security**: Cryptographically secure generation
+4. **Standards Compliance**: RFC 9562 adherence
+
+### Decision 3: Railtie-Based Integration
+
+#### Chosen: Automatic Railtie Integration
+```ruby
+# lib/rails_uuid_pk/railtie.rb
+module RailsUuidPk
+  class Railtie < ::Rails::Railtie
+    initializer "rails_uuid_pk.configure" do
+      ActiveSupport.on_load(:active_record) do
+        ActiveRecord::Base.include HasUuidv7PrimaryKey
+      end
+    end
+  end
+end
+```
+
+#### Benefits
+- **Zero Configuration**: Works immediately after bundle install
+- **Convention over Configuration**: Follows Rails patterns
+- **Backwards Compatible**: Doesn't break existing applications
+- **Automatic**: No manual model changes required
+
+#### Alternative: Explicit Inclusion
+```ruby
+# Would require developers to add to each model
+class User < ApplicationRecord
+  include RailsUuidPk::HasUuidv7PrimaryKey
+end
+```
+
+### Decision 4: Database Adapter Extension Pattern
+
+#### Chosen: Selective Adapter Extensions
+**PostgreSQL**: No extension needed - uses Rails' native UUID type support
+**MySQL & SQLite**: Custom extensions for VARCHAR(36) UUID storage
+
+```ruby
+# MySQL extension - provides VARCHAR(36) type mapping
+# lib/rails_uuid_pk/mysql2_adapter_extension.rb
+module RailsUuidPk
+  module Mysql2AdapterExtension
+    def native_database_types
+      super.merge(uuid: { name: "varchar", limit: 36 })
+    end
+
+    def register_uuid_types(m = type_map)
+      m.register_type(/varchar\(36\)/i) { RailsUuidPk::Type::Uuid.new }
+    end
+  end
+end
+
+# SQLite extension - provides VARCHAR(36) type mapping
+# lib/rails_uuid_pk/sqlite3_adapter_extension.rb
+module RailsUuidPk
+  module Sqlite3AdapterExtension
+    def native_database_types
+      super.merge(uuid: { name: "varchar", limit: 36 })
+    end
+
+    def register_uuid_types(m = type_map)
+      m.register_type(/varchar\(36\)/i) { RailsUuidPk::Type::Uuid.new }
+    end
+  end
+end
+```
+
+#### Benefits
+- **Database-Specific Optimization**: Each database gets appropriate handling
+- **Clean Separation**: Adapter concerns are isolated
+- **Extensible**: Easy to add new database support
+- **Testable**: Each adapter can be tested independently
+
+### Decision 5: Opt-out Mechanism for Selective UUID Generation
+
+#### Chosen: Class-Level Opt-out with Migration Helper Integration
+```ruby
+# lib/rails_uuid_pk/concern.rb
+module RailsUuidPk
+  module HasUuidv7PrimaryKey
+    extend ActiveSupport::Concern
+
+    module ClassMethods
+      def use_integer_primary_key
+        @uses_integer_primary_key = true
+      end
+
+      def uses_uuid_primary_key?
+        !@uses_integer_primary_key
+      end
+    end
+
+    included do
+      before_create :assign_uuidv7_if_needed, if: -> { id.nil? && self.class.uses_uuid_primary_key? }
+    end
+  end
+end
+```
+
+#### Migration Helper Integration
+```ruby
+# lib/rails_uuid_pk/migration_helpers.rb
+def references(*args, **options)
+  ref_name = args.first
+  ref_table = options.delete(:to_table) || ref_name.to_s.pluralize
+
+  # Automatic type detection for mixed PK scenarios
+  if uuid_primary_key?(ref_table)
+    options[:type] = :uuid
+  end
+
+  super(*args, **options)
+end
+```
+
+#### Migration Schema Updates
+When opting out of UUID primary keys, developers must also modify the generated migration:
+
+```ruby
+# Generated migration (modify this line)
+create_table :legacy_models, id: :uuid do |t|  # Change :uuid to :integer
+  t.string :name
+end
+
+# After modification
+create_table :legacy_models, id: :integer do |t|  # Now uses integer primary keys
+  t.string :name
+end
+```
+
+#### Benefits
+- **Selective Control**: Individual models can opt out while maintaining overall UUID usage
+- **Migration Intelligence**: Automatic foreign key type detection for mixed scenarios
+- **Zero Breaking Changes**: Existing applications continue to work unchanged
+- **Clean API**: Simple declarative syntax for opting out
+- **Inheritance Aware**: Subclasses must explicitly opt out (no automatic inheritance)
+
+#### Trade-offs
+- **Inheritance Behavior**: Opt-out is not inherited - each model must explicitly declare preference
+- **Migration Complexity**: Foreign key type detection becomes more complex in mixed environments
+- **Testing Requirements**: Mixed scenarios require additional test coverage
+
+## Migration Performance Implications
+
+### Schema Inspection Caching
+```ruby
+# lib/rails_uuid_pk/migration_helpers.rb
+def uuid_primary_key?(table_name)
+  @uuid_pk_cache ||= {}
+  return @uuid_pk_cache[table_name] if @uuid_pk_cache.key?(table_name)
+
+  # Database schema inspection
+  conn = connection
+  pk_column = find_primary_key_column(table_name, conn)
+  @uuid_pk_cache[table_name] = !!(pk_column && pk_column.sql_type =~ /uuid|varchar\(36\)/)
+end
+```
+
+**Performance Impact**:
+- **Caching**: Reduces database queries during migrations
+- **Memory**: Small memory footprint for cache
+- **Accuracy**: Cache is per-migration instance, ensuring freshness
+
+### Foreign Key Type Detection
+```ruby
+def references(*args, **options)
+  ref_name = args.first
+  ref_table = options.delete(:to_table) || ref_name.to_s.pluralize
+
+  # Automatic type detection
+  if uuid_primary_key?(ref_table)
+    options[:type] = :uuid
+  end
+
+  super(*args, **options)
+end
+```
+
+**Benefits**:
+- **Automatic**: No manual foreign key type specification
+- **Correct**: Ensures type consistency across relationships
+- **Polymorphic**: Handles complex association scenarios
+
+## Database Replication and Backup Considerations
+
+### Replication Compatibility
+- **UUID Generation**: App-level generation is replication-safe
+- **No Conflicts**: UUIDs are globally unique by design
+- **Ordering**: Time-based UUIDs maintain logical ordering across replicas
+
+### Backup and Restore
+- **Data Integrity**: UUIDs remain valid across backup/restore cycles
+- **References**: Foreign key relationships preserved
+- **Consistency**: No auto-increment conflicts or renumbering issues
+
+### Multi-Region Deployments
+- **Global Uniqueness**: UUIDs work across geographically distributed systems
+- **Conflict Resolution**: No primary key conflicts in multi-master setups
+- **Audit Trails**: Time-based UUIDs enable global event ordering
+
+## ORM and Query Builder Impact
+
+### ActiveRecord Integration
+- **Seamless**: Works with all ActiveRecord features
+- **Associations**: Supports belongs_to, has_many, has_one relationships
+- **Validations**: Compatible with all Rails validations
+- **Callbacks**: Integrates with Rails callback system
+
+### Query Performance
+- **Index Usage**: Leverages database indexes effectively
+- **Range Queries**: UUIDv7 enables efficient time-based queries
+- **Join Performance**: Foreign key relationships perform well
+- **Batch Operations**: Compatible with find_each, find_in_batches
+
+### Development Experience
+- **No Code Changes**: Existing Rails code works unchanged
+- **Migration Helpers**: Automatic foreign key type detection
+- **Schema Dumping**: Compatible with Rails schema tools
+- **Testing**: Works with all Rails testing frameworks
+
+## Error Handling and Resilience
+
+### Database Connection Failures
+```ruby
+def uuid_primary_key?(table_name)
+  conn = connection
+  return false unless conn.respond_to?(:table_exists?) && conn.table_exists?(table_name)
+
+  # Graceful fallback on errors
+  pk_column = find_primary_key_column(table_name, conn)
+  !!(pk_column && pk_column.sql_type =~ /uuid|varchar\(36\)/)
+rescue => e
+  # Log warning and return false on connection errors
+  Rails.logger.warn "rails-uuid-pk: Could not check table #{table_name}: #{e.message}"
+  false
+end
+```
+
+### Schema Inconsistencies
+- **Defensive Programming**: Handles missing tables gracefully
+- **Type Safety**: Validates UUID format before database operations
+- **Migration Safety**: Works during schema changes and rollbacks
+
+## Future Evolution Considerations
+
+### Extensibility Points
+- **Configuration System**: Planned configuration options for customization
+- **Plugin Architecture**: Extensible adapter system for new databases
+- **Performance Monitoring**: Optional telemetry and metrics collection
+
+### Migration Path
+- **Backwards Compatibility**: Current design supports gradual migration
+- **Version Pinning**: Semantic versioning for breaking changes
+- **Deprecation Warnings**: Clear communication of deprecated features
+
+### Performance Optimizations
+- **Native Database Functions**: Future option for database-level generation
+- **Bulk Operations**: Optimized handling for large data imports
+- **Index Strategies**: Advanced indexing recommendations
+
+## Conclusion
+
+The rails-uuid-pk architecture prioritizes **compatibility**, **simplicity**, and **performance** while maintaining **security** and **reliability**. Key decisions like app-level UUID generation and Railtie-based integration enable the zero-configuration experience while ensuring robust operation across diverse Rails applications and database environments.
+
+The architecture successfully balances competing concerns:
+- **Developer Experience**: Zero-configuration adoption
+- **Database Compatibility**: Works across PostgreSQL, MySQL, and SQLite
+- **Performance**: UUIDv7 provides better characteristics than alternatives
+- **Maintainability**: Clean, modular design with clear separation of concerns
+- **Future-Proofing**: Extensible architecture for ongoing evolution
+
+This architectural foundation enables rails-uuid-pk to serve as a reliable, production-ready solution for UUID primary keys in Rails applications.

data/CHANGELOG.md

@@ -5,6 +5,68 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v1.0.0.html).
 
+## [0.13.0] - 2026-01-20
+
+### Added
+- **`rails_uuid_pk:add_opt_outs` Rails Generator**: New generator to automatically add `use_integer_primary_key` to models with integer primary keys in existing applications
+  - Scans all ActiveRecord models in `app/models/**/*.rb`
+  - Inspects database schema to detect integer primary keys
+  - Adds `use_integer_primary_key` calls to eligible models
+  - Command-line options: `--dry-run` (preview changes), `--verbose` (detailed output)
+  - Idempotent operation - safe to run multiple times
+  - Comprehensive error handling and user feedback
+- **Trilogy Adapter Support**: Added support for the trilogy gem as an alternative to mysql2 for MySQL connections
+  - New `TrilogyAdapterExtension` module for trilogy adapter integration
+  - Automatic detection and registration of trilogy adapter for UUID type support
+  - Comprehensive test suite for trilogy adapter functionality
+  - Updated documentation to reflect trilogy compatibility alongside mysql2
+  - Added trilogy as development dependency for testing
+
+### Changed
+- **Documentation Consistency**: Ensured all documentation files consistently communicate that UUIDv7 is the default behavior, while opt-out functionality exists for exceptional cases (legacy tables, third-party integrations, etc.)
+
+### Documentation
+- **Clarified Default UUIDv7 Behavior**: Updated all documentation files to explicitly state that rails-uuid-pk assumes UUIDv7 primary keys by default for all models, with `use_integer_primary_key` being an exception for models requiring integer primary keys
+  - **README.md**: Emphasized "Assumes UUIDv7 primary keys by default" and clarified opt-out as "Exception: Opting Out"
+  - **ARCHITECTURE.md**: Updated "Zero-Configuration Philosophy" to highlight automatic UUIDv7 primary keys by default
+  - **DEVELOPMENT.md**: Clarified opt-out functionality as "exceptions only" for specific use cases
+  - **AGENTS.md**: Updated project overview to state "automatically assumes UUIDv7 primary keys by default... Models requiring integer primary keys are treated as exceptions"
+- **Bulk Operations Documentation**: Added comprehensive documentation about bulk operations performance and limitations across README.md and PERFORMANCE.md, explaining that UUIDs are not automatically generated during bulk insert operations (`insert_all`, `upsert_all`, `Model.import`) and require manual UUID assignment using `SecureRandom.uuid_v7`, while highlighting the significant performance benefits when properly implemented
+
+### Technical Details
+- Added `lib/generators/rails_uuid_pk/add_opt_outs_generator.rb` with full Rails generator implementation
+- Added `lib/generators/rails_uuid_pk/templates/.keep` for directory structure maintenance
+- Added `test/generators/add_opt_outs_generator_test.rb` with comprehensive test suite (9 tests, 18 assertions)
+- Added `test/railtie_test.rb` with dedicated railtie functionality tests
+- Updated `lib/rails_uuid_pk.rb` to load generator components
+- Generator includes smart model file parsing, database schema inspection, and safe file modification
+- Full cross-database compatibility (PostgreSQL, MySQL, SQLite)
+- Production-ready with proper error handling and logging integration
+- Added `lib/rails_uuid_pk/trilogy_adapter_extension.rb` with trilogy-specific adapter extension
+- Updated `lib/rails_uuid_pk/railtie.rb` to include trilogy adapter hooks and type registration
+- Updated `lib/rails_uuid_pk.rb` to load trilogy adapter extension
+- Added `test/database_adapters/trilogy_test.rb` with comprehensive trilogy adapter tests
+- Added trilogy database configuration to test suite
+- Updated gemspec with trilogy development dependency
+- Enhanced README.md and gemspec descriptions to mention trilogy support
+
+### Fixed
+- **Migration Helpers Robustness**: Enhanced primary key detection with improved error handling and safety checks
+  - Added safe navigation operators (`&.`) for `sql_type` access to prevent `NoMethodError` on nil objects
+  - Added comprehensive error handling with rescue blocks for database connection failures
+  - Restricted UUID primary key detection to only consider standard Rails primary keys named 'id'
+  - Graceful fallback to integer foreign keys when database operations fail
+
+### Testing
+- **Comprehensive Test Suite Expansion**: Added extensive test coverage for edge cases and error scenarios
+  - Added `test/railtie_test.rb` with 1 test covering railtie connection registration logic
+  - Expanded `test/configuration/setup_test.rb` with 5 additional tests (12 total) covering railtie UUID type registration, database configurations, migration helpers inclusion, adapter extension registration, and schema format configuration
+  - Enhanced `test/database_adapters/mysql_test.rb` with 1 additional test for MySQL adapter extension `configure_connection` behavior
+  - Enhanced `test/database_adapters/sqlite_test.rb` with 1 additional test for SQLite adapter extension transaction-aware configuration
+  - Enhanced `test/database_adapters/uuid_adapter_extension_test.rb` with 2 additional tests covering `type_to_dump` functionality and migration helpers edge cases
+  - Expanded `test/migration_helpers/references_test.rb` with 6 additional tests (11 total) covering polymorphic associations with mixed primary key types, nil options handling, empty polymorphic options, column lookup error handling, method chaining safety, and rescue block behavior
+  - Total test expansion: 16 new tests across 6 test files, improving robustness and edge case coverage
+
 ## [0.12.0] - 2026-01-17
 
 ### Changed