I havent worked with MySQL replication but Google has designed a number of tools regarding MySQL master/slave:
http://google-code-updates.blogspot.com/2007/04/google-releases- patches-that-enhance.html as far as a within-SQLAlchemy system to issue SQL INSERT/UPDATE/ DELETE to more than one place simultaneously, we have had some plans to build a full "clustering" framework supporting hooks for this but its a TODO. We've previously had "ProxyEngine" classes but the architecture of SA's engine has changed since that was written - its still possible to embed a "proxying" execution context into an engine with a little bit of tinkering though (if you were to work that up, then we'd have our new ProxyEngine). Other people have written "replication" solutions using ORM sessions, particularly using MapperExtensions to issue a second SQL statement. I think thats pretty hacky though. I think the cleanest way would be to get it working at the MySQL level. On Oct 8, 2007, at 6:11 AM, Jakub Stolarski wrote: > > Hi, > > I want to do something like this: > - two hosts with databases (MySQL) - master and slave > - enabled replication (master - read/write, slave - read only if > master is broken) > > Can you help me and suggest how to do this using SQLAlchemy? > Do I have to write some proxy or write custom connection pool? > > If there were some ready to use proxy I can use them. I tried > MySQLProxy, but it can't make distinction between read and write > databases. > > Thank you for help. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
