SessionTransaction will start transactions across any number of databases, as different engines come into its querying scope. when SessionTranasction commits, it commits all underlying transacitons. so if you want to start all transactions "at once", you can create a new SessionTransaction, and just add() each engine you want. at the point of add(), it retrieves a connection from the pool and calls begin() on it.
however, this is not using two phase commit, which means that if one commit fails, all previous commit's stay committed. if you want true two phase commit I'd look into Zalchemy which has this feature. On Mar 20, 2007, at 1:47 AM, Benno Rice wrote: > > Hi, > > I'm wondering if it would be possible to have a situation where > transactions coming in from the ORM system could be sent to multiple > database servers at once. > > If I were to look into adding this, where would be the best place to > start? > > Many thanks. > > -- > Benno Rice > [EMAIL PROTECTED] > http://jeamland.net/ > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
