So, last night I asked the RORO Sydney group what they were doing when their
list of migrations got too long with migrations that have lots of new columns
added/changed etc, and some people suggested that periodically it's good to
trim them back, assuming that all the DBs you will deploy to are in the same
state.
I'm wondering, what's the actual best way to go about this?
I was thinking of doing:
rake db:schema:dump
rename the schema file and edit it into being a "beginning" migration, then
delete the old migrations?
What do other people do?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" 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/rails-oceania?hl=en
-~----------~----~----~----~------~----~------~--~---
