change_table transformations

[judearasu]

Is it fine to write the change_table transformation on

https://github.com/rails/rails/blob/master/activerecord/lib/active_record/migration.rb

As it is not available on the migration file

change_table(:suppliers) do |t|
t.column :name, :string, :limit => 60

Other column alterations here

end

[bobbywilson0]

It's not clear what you are asking. Can you please describe the issue in more detail or close it?

[judearasu]

@Bobbyw In activerecord/lib/active_record/migration.rb file create_table, drop_table & rename_table has been documented, is it fair enough to document change_table on transformations list or not ?

#create_table(name, options) Creates a table called +name+ and
#makes the table object available to a block that can then add columns to it,
#following the same format as add_column. See example above. The options hash
#is for fragments like "DEFAULT CHARSET=UTF-8" that are appended to the create
#table definition.
# drop_table(name): Drops the table called +name+.
#* rename_table(old_name, new_name): Renames the table called +old_name+

to +new_name+.

[bobbywilson0]

Ah I see what you are saying now. change_table is defined here http://api.rubyonrails.org/classes/ActiveRecord/ConnectionAdapters/SchemaStatements.html#method-i-change_table So I don't know if it makes the most sense to document it in migrations, although I understand it is relevant, and the provided documentation on change_table is pretty slim.

Someone more involved than myself would be better to make this decision. @steveklabnik is a nice guy and might be able to provide some insight.

[frodsan]

@judearasu Is this works for you? https://github.com/lifo/docrails/commit/c5647a08b4a6ece80379306d9f148608e2597d83#L0R104

[rafaelfranca]

I think so. CLosing this one. Thanks @frodsan