Note that I said that OrientDB has the capability to implement it (I think) but doesn't at this time.
On Sat, Nov 7, 2015 at 11:41 AM, pieter <[email protected]> wrote: > Ok tx, I'll have a look for it in OrientDB. > > On 07/11/2015 18:29, Stephen Mallette wrote: > > I think OrientDB could, but didn't in 2.x. > > > > On Sat, Nov 7, 2015 at 11:10 AM, pieter <[email protected]> wrote: > > > >> Hi, > >> > >> Just as a matter of interest do you know of any graph that supports this > >> except for Titan? > >> > >> Cheers > >> Pieter > >> > >> On 07/11/2015 16:20, stephen mallette (JIRA) wrote: > >>> stephen mallette created TINKERPOP3-947: > >>> ------------------------------------------- > >>> > >>> Summary: Enforce semantics of threaded transactions as > >> manual > >>> Key: TINKERPOP3-947 > >>> URL: > >> https://issues.apache.org/jira/browse/TINKERPOP3-947 > >>> Project: TinkerPop 3 > >>> Issue Type: Improvement > >>> Components: structure > >>> Affects Versions: 3.1.0-incubating > >>> Reporter: stephen mallette > >>> Assignee: Marko A. Rodriguez > >>> Priority: Minor > >>> > >>> > >>> Threaded transactions are manual in nature. They open when > >> {{createThreadedTransaction}} is called and they are created then when > >> closed, should not be re-used. If you need a new one you should call > >> {{createdThreadedTransaction}} again. Those semantics are not enforced > by > >> TinkerPop anywhere i the test suite, but that's typically how this > feature > >> is used. > >>> > >>> > >>> -- > >>> This message was sent by Atlassian JIRA > >>> (v6.3.4#6332) > >> > >
