On Wed, Mar 2, 2011 at 3:59 PM, Gaba Luschi <[email protected]> wrote:
> Are migrations used only when you're making changes to a database? Does > it just allow the developer to avoid using raw SQL when working with > databases? > Right. Not only does it allow the developer to use a much easier (IMO) manner to do things like add, modify columns, tables, etc, it also keeps a record of the progression of your database schema. Migrations also include the ability (assuming it is used) to roll back any changes with a command from a terminal. At times a migration may also contain data-transforming tasks or really any other ruby code one needs to write to complete the migration. > > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
