Does anyone have MySQL replication set up for a Rails App that uses
migrations? I''m having an issue where every time I run a migration
Rails is trying to create the schema_info table.
Mysql::Error: Table ''schema_info'' already exists: CREATE TABLE
schema_info (version int(11))
This causes a problem on the slave databases where the replicated
create table statement causes an error that stops the slave''s SQL
thread.
I''m wondering if there is a reason why the migrations framework keeps
trying to create the table, rather than checking for its existence
first.
Thanks in advance.
Erik
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
