You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Bryn Cooke (JIRA)" <ji...@apache.org> on 2015/06/26 12:14:05 UTC
[jira] [Created] (TINKERPOP3-749) Consider moving
Transaction.create() on to Graph.createTx()
Bryn Cooke created TINKERPOP3-749:
-------------------------------------
Summary: Consider moving Transaction.create() on to Graph.createTx()
Key: TINKERPOP3-749
URL: https://issues.apache.org/jira/browse/TINKERPOP3-749
Project: TinkerPop 3
Issue Type: Improvement
Reporter: Bryn Cooke
Priority: Minor
Currently if you want to create a thread independent transaction you do:
Transaction t = g.tx(); //My current transaction.
Graph tg = t.create(); //Creating a new transaction.
I know this may seem petty, but to me it says that I am creating a new transaction that is a child of the Transaction obtained via tx().
Does this mean that if do:
t.commit();
it will commit all spawned transactions?
Just thinking it would be nicer to have Graph.createTx() in addition to Graph.tx() that way it doesn't look like there is any hierarchy of transactions.
Fully understand if others don't see it that way though.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)