schema_ferry 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a34cb64f18cd33a93ebbc3636bd1e76e170279d98ec5d9c59b8ef14e8f141fd9
-  data.tar.gz: f3ae1fbea45f7b7f5c4d5c79e5704fcc680955a77a9123a73975618c32752b8f
+  metadata.gz: ffeee05f1fb01ebb90d2a75df3077d46788714b4aa192de62f7f9b4f62c1824c
+  data.tar.gz: 4977e0f544613fd09d6d61674407b281463e2fca75770d8b21aea0e60f94de44
 SHA512:
-  metadata.gz: 9fa8d644af36d128f1922258299fc96ba682a068f1195fced8e8446e64067c63e5d5ee81b3541f07e162d0e2588495946e111ca5076da608ab9054491f9a8cdd
-  data.tar.gz: 18dd78144c3e9ccbba232da685b0248eb22be16a73ac55090edfe6638a7d93d8ef794bcf1babad248a95f324b9bf8a3e4bac4e3db19a2b4d735d09dd45a9cffe
+  metadata.gz: 9fc86363dac3a3bcb9e4bbf852ef3a5f5ea7113dbf6c9722cf0741b666b49da056b4334d866fec935e4255aff0ae72ffa943d1b028f966edfc5caa433a04f6ca
+  data.tar.gz: a6a95a90bfd5ddbcbfcc4bc25de2ab3036c68f5d9d272478bf74a1c0980ca8fb19bf1c01425db83cbc6b0ed87adac02a64ff0977b91d12d5cbc30e57fda909ae

data/CHANGELOG.md

@@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.1.3] - 2026-07-06
+
+### Fixed
+
+- The 0.1.2 fix only covered the two reported cases, not the underlying pattern: any type/option combination that PostgreSQL can't actually reproduce back to ActiveRecord causes `apply!` to re-run `change_column` forever, because ridgepole compares the declaration against a state it can never match.
+  - `DOUBLE` columns (`:float`) are read with `limit: 53` (the type's internal bit width), but a PostgreSQL column never reports a limit back. `limit` is no longer emitted for `:float` columns.
+  - Plain `DECIMAL` columns with a default (not just ones bumped from `BIGINT UNSIGNED`) now render their default as a string, matching the form ActiveRecord's schema dumper uses for decimal defaults — the same fix from 0.1.2, generalized to `TypeMapper` so it applies to every decimal column instead of only the unsigned-bigint conversion path.
+
 ## [0.1.2] - 2026-07-06
 
 ### Fixed

data/lib/schema_ferry/converter/column_converter.rb

@@ -45,11 +45,7 @@ module SchemaFerry
         else
           emit_warning "column #{raw[:name].inspect}: BIGINT UNSIGNED has no PostgreSQL " \
                        "integer equivalent; mapped to decimal(20, 0)."
-          # AR's schema dumper renders decimal defaults as a string (e.g.
-          # `default: "0"`), not a numeric literal — match that representation
-          # or ridgepole re-applies the default on every run.
-          new_default = raw[:default]&.to_s
-          raw.merge(type: :decimal, limit: nil, precision: 20, scale: 0, default: new_default)
+          raw.merge(type: :decimal, limit: nil, precision: 20, scale: 0)
         end
       end
 

data/lib/schema_ferry/converter/type_mapper.rb

@@ -3,9 +3,10 @@
 module SchemaFerry
   module Converter
     class TypeMapper
-      # PG has no limit concept for text/binary/bigint; drop the MySQL-derived
-      # limits.
-      LIMIT_STRIPPED_TYPES = %i[text binary bigint].freeze
+      # PG has no limit concept for text/binary/bigint/float; drop the
+      # MySQL-derived limits (float's limit: 53 is DOUBLE's internal bit
+      # width, not something AR ever reads back from a PG column).
+      LIMIT_STRIPPED_TYPES = %i[text binary bigint float].freeze
 
       # PG's default timestamp precision is 6. Spelling it out makes ridgepole
       # see a diff against the PG export (which omits it) on every run.
@@ -43,8 +44,15 @@ module SchemaFerry
         pg_type, adjusted = normalize_integer(adjusted) if pg_type == :integer
         adjusted.delete(:limit) if LIMIT_STRIPPED_TYPES.include?(pg_type)
         strip_default_precision(pg_type, adjusted)
-        # PG numeric(20) equals numeric(20,0) and is exported without scale.
-        adjusted[:scale] = nil if pg_type == :decimal && adjusted[:scale]&.zero?
+        if pg_type == :decimal
+          # PG numeric(20) equals numeric(20,0) and is exported without scale.
+          adjusted[:scale] = nil if adjusted[:scale]&.zero?
+          # AR's schema dumper renders decimal defaults as a string (e.g.
+          # `default: "0"`), not a numeric literal. ridgepole compares against
+          # that dumped form, so a BigDecimal/Integer default never matches
+          # and gets re-applied on every run.
+          adjusted[:default] = adjusted[:default]&.to_s
+        end
 
         [pg_type, adjusted]
       end

data/lib/schema_ferry/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module SchemaFerry
-  VERSION = "0.1.2"
+  VERSION = "0.1.3"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: schema_ferry
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - kyuuri1791