Re: Documentation question: Section 10.6 Nested Transactions
Jason Plurad <plu...@...>
toggle quoted message Show quoted text
Let's say Transaction A from the example begins first and sets v2 uniqueName=foo. Transaction A takes a long time to "do many other things", so it is not committed yet.
Transaction B then begins and creates a v3 vertex with uniqueName=foo. v3 is able to set uniqueName=foo because it is isolated from Transaction A and has no idea that v2 wants to set uniqueName=foo.
Transaction B is committed first. When Transaction A calls graph.tx().commit(), it will throw an exception because uniqueName=foo on v2 conflicts with v3.
Does that make sense? We could add more words to the doc to clarify if necessary.
On Monday, January 15, 2018 at 5:45:11 AM UTC-5, graham_wallis wrote: