Tyler Smart wrote: > Most of my migrations are by number, not timestamp, but 5 or 6 of them > (the most recent) are with timestamp. These I want to move to number > based, and now I want to forward the migration table to the appropriate > number. How do I force the table to update without actually running the > migration, or should I migrate down to 5 or 6 ago (before timestamp) and > then migrate up again with numbers?
You don't want to do any of this. Timestamped migrations are the default in Rails, and there's really no good reason to avoid there use AFAIK. What's your ultimate goal? Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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.
