Hi Jonathan,
On 03/03/2014 17:22, Jonathan Vanasco wrote:
Yep. You can look at the internals of the 'Transaction' package and
cross reference to the zope.sqlachemy to see exactly how it works.
Sorry, not sure if I'm following you, but I'm talking about Simon's
suggestion only to use a sqlalchemy session and deliberately *not* using
zope's transaction package or zope.sqlalchemy.
cheers,
Chris
IIRC, the implementation of the two phase commit basically has everyone
flush on Phase1, then report back as a "vote". If there are any
negative votes, the transaction manager instructs everyone to fail and
rollback as Phase2. If you had a flush that caused an integrity error
before trying to commit, that would still trigger an issue.
--
You received this message because you are subscribed to the Google
Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/groups/opt_out.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/groups/opt_out.
