Problem: When you alter tables in the free version of MySql (not Enterprise) running on a master / slave or master / master replication, the replication will stop in it''s tracks on any "ALTER TABLE" commands to one of the servers. Because rails uses this in migration. Does anyone have a way of going about preventing this from happening, while the database is still live? My only suggestion is stopping the database replication. Running migration on both servers, then starting it again. But this is really risky I find. Any other solutions? --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---