Question

Granted, one could use property :foo, Text, lazy: false all over the place to replace property :foo, String but that, of course, defeats several purposes in one go. Or I could use manual migrations, which I have been doing—I’m looking around now to see if they can finally be abandoned, insofar as VARCHAR v. TEXT is concerned.

In other words, I’d like automigrate to create TEXT fields for PostgreSQL for models with String properties rather than arbitrarily, pointlessly, constrained VARCHAR atop a TEXT.

Answer 1

Here’s a lousy but working solution I came up with—if you’ve better one please add it and I’ll accept that instead.

In config/initializers/postgresql_strings.rb

module DataMapper
  module Migrations
    module PostgresAdapter
      def self.included(base)
        base.extend ClassMethods
      end

      module ClassMethods

        def type_map
          precision = Property::Numeric.precision
          scale     = Property::Decimal.scale

          super.merge(
            Property::Binary => { :primitive => 'BYTEA' },
            BigDecimal => { :primitive => 'NUMERIC', :precision => precision, :scale => scale },
            Float => { :primitive => 'DOUBLE PRECISION' },
            String => { :primitive => 'TEXT' } # All that for this
          ).freeze
        end
      end

    end
  end
end

# If you're including dm-validations, it will surprisingly attempt
# to validate strings to <= 50 characters, this prevents that.
DataMapper::Property::String.auto_validation(false)