Changeset 8304
- Timestamp:
- 12/05/07 20:20:37 (1 year ago)
- Files:
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/activerecord/CHANGELOG
r8298 r8304 1 1 *SVN* 2 3 * 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] 2 4 3 5 * More complete documentation for find_by_sql. Closes #7912 [fearoffish] trunk/activerecord/lib/active_record/connection_adapters/abstract/schema_definitions.rb
r8285 r8304 293 293 294 294 # Instantiates a new column for the table. 295 # The +type+ parameter must be one of the following values: 295 # The +type+ parameter is normally one of the migrations native types, 296 # which is one of the following: 296 297 # <tt>:primary_key</tt>, <tt>:string</tt>, <tt>:text</tt>, 297 298 # <tt>:integer</tt>, <tt>:float</tt>, <tt>:decimal</tt>, 298 299 # <tt>:datetime</tt>, <tt>:timestamp</tt>, <tt>:time</tt>, 299 300 # <tt>:date</tt>, <tt>:binary</tt>, <tt>:boolean</tt>. 301 # 302 # You may use a type not in this list as long as it is supported by your 303 # database (for example, "polygon" in MySQL), but this will not be database 304 # agnostic and should usually be avoided. 300 305 # 301 306 # Available options are (none of these exists by default):