Re: XA transaction isolation level and ACID properties
I'm operating a cluster of a few dozen different database masters.
All application transactions occur at READ COMMITTED isolation level.
Application developers are wishing to commit data to multiple db masters in at least an eventually consistent fashion (ideally atomic, but what isn't acceptable is data being committed to db1 but failing to ever be committed to db2). I wish to build out the tooling to enable such a feature.
Subject
Views
Written By
Posted
2540
April 14, 2016 05:36PM
944
April 15, 2016 03:33PM
Re: XA transaction isolation level and ACID properties
952
April 16, 2016 04:05PM
880
April 16, 2016 06:57PM
927
April 18, 2016 12:17AM
829
April 18, 2016 10:25AM
902
April 18, 2016 04:24PM
862
April 18, 2016 05:50PM
868
April 18, 2016 07:38PM
983
April 18, 2016 10:48PM
951
April 19, 2016 08:21AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.