I'm looking for a way to have my DB replicated in REAL TIME to be used
in case I lose my primary copy.
I saw that the two phase commit exist but I'm not sure if that is the
correct option. I have the feeling that it would be abusing a
mechanism purposed for correlating to separate DBs and not creating
replications.
Maybe holding two (or several) separate sessions and maintaining the
duplication is the right choice?
Can anyone advise on the following:
1. What would be the preferred method to have that ready backup?
2. If using the 2 phase commit:
a. Can I detect which of the engines/DBs failed to commit?
b. Can I change my session's configuration (binds setup) to remove
the two phase? Notice that I have uncommitted data in the session
which I CANNOT lose.
3. Would an approach of holding several separate sessions be the right
one?
Thanks
Vic
--~--~---------~--~----~------------~-------~--~----~
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
sqlalchemy+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
