Fritz Trapper wrote: > Marnen Laibow-Koser wrote: >> How? You're not normally going to be running old migrations. What >> specific problem do you think you will run into if you leave the old >> migrations around? > > I moved the complete database from my interim server to the permanent > one.
Then the schema_migrations table should have the correct values, so Rake will know not to run the old migrations. [...]. > > On my developmentsystem, they're still present and dont harm, but I > guess, they will be pushed up to the server again with my next update > and will get run, because there is no corresponding entry in the > migration data base. > Why aren't there? If the migration was run, its ID will be in the schema_migrations table. > Maybe, the simplest solution will be, to do something to make them null > migrations on the development system. And the right way to do that is to make sure that their IDs are in schema_migrations. 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.
