> ActiveRecord -- the part of Rails responsible for talking to the > database -- does not support the configuration of multiple data > sources for the purposes of segmenting reads and writes and directing > them to different mysql servers on that basis, at this time, as far as > I know.
[skip] > Alternatively, you could use multi-master replication. If you go this > route you'll need to address issues pertaining to auto_increment > collisions. This is fairly easy with MySQL 5 as it has global > variables for auto_increment_increment and auto_increment_offset. [skip] > -- > benjamin Hi, Thanks for this guide light. I will think about patch. As About two-way replication then I thought about it. Unfortunately I do not have experience with it. I am only using one-way (old approved method). Could please you share your experience if you have used MySQL with two-way replication and give me your feedback how it works. Thanks again. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
