You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/06/26 21:18:04 UTC

[jira] [Closed] (TINKERPOP3-749) Consider moving Transaction.create() on to Graph.createTx()

     [ https://issues.apache.org/jira/browse/TINKERPOP3-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP3-749.
---------------------------------------
    Resolution: Implemented

Implemented at:

https://github.com/apache/incubator-tinkerpop/commit/2c5474be0e6c79d665e8d68bf616db6c9cb1b435

> 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
>          Components: structure
>            Reporter: Bryn Cooke
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.0.0.GA
>
>
> 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)