From 632ab246db10bf15939df8d6bfc5f964dd61ef5b Mon Sep 17 00:00:00 2001 From: Marcel Molina Date: Wed, 5 Dec 2007 20:20:37 +0000 Subject: Reveal that the type option in migrations can be any supported column type for your database but also include caveat about agnosticism. Closes #7531 [adamwiggins, mikong] git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@8304 5ecf4fe2-1ee6-0310-87b1-e25e094e27de --- .../connection_adapters/abstract/schema_definitions.rb | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'activerecord/lib') diff --git a/activerecord/lib/active_record/connection_adapters/abstract/schema_definitions.rb b/activerecord/lib/active_record/connection_adapters/abstract/schema_definitions.rb index 86ff16531f..2aa8a12228 100644 --- a/activerecord/lib/active_record/connection_adapters/abstract/schema_definitions.rb +++ b/activerecord/lib/active_record/connection_adapters/abstract/schema_definitions.rb @@ -292,12 +292,17 @@ module ActiveRecord end # Instantiates a new column for the table. - # The +type+ parameter must be one of the following values: + # The +type+ parameter is normally one of the migrations native types, + # which is one of the following: # :primary_key, :string, :text, # :integer, :float, :decimal, # :datetime, :timestamp, :time, # :date, :binary, :boolean. # + # You may use a type not in this list as long as it is supported by your + # database (for example, "polygon" in MySQL), but this will not be database + # agnostic and should usually be avoided. + # # Available options are (none of these exists by default): # * :limit - # Requests a maximum column length (:string, :text, -- cgit v1.2.3