Hassan Schroeder wrote: > > And yet I still fail to see the evidence supporting this as a > "convention", > especially given that the API includes examples of using migrations to > *change data*, *not* just structure. > > http://api.rubyonrails.org/classes/ActiveRecord/Migration.html >
Well... Alright - one migration creates an index, and another one removes empty tags. This is a one-time change to the data, which would be necessary as a migration but would not show up in the schema.rb file. The original comment was "Don't seed with migrations - seed with the seeding process". This is still a good idea. :) -- 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.
