Closed fppt closed 8 years ago
hmm, this sounds like a bug. maybe it's related with the automated prefixing of the class name, i.e. V and E? see https://github.com/mpollmeier/orientdb-gremlin#labels-and-classes
Can you check the names of the created classes in the two cases addVertex
and createVertexClass
?
Hi mpollmeier,
I think it is a bug because when I watch the following classes:
graph.database.browseClass("TYPE")
graph.database.browseClass("V_TYPE")
they both throw exceptions initially, but after createVertexClass
"TYPE" is valid and after addVertex
"V_TYPE" is valid. So it appears addVertex
appends the V
and createVertexClass
does not.
For fun I tried to "fix" this issue: https://github.com/mpollmeier/orientdb-gremlin/pull/89 . Apologies if I am way off base. I thought it might be a good way to get more into the code.
Fixed with the referenced PR.
Hi,
I am a bit confused with regards to how orient is handling the
tx()
method. Specifically, if I do the following:Everything appears to work. If I change the second
graph = factory.getNoTx();
tograph = factory.getTx();
, then it fails.Similarly if I make the 2nd to last commit
graph.tx().commit();
it fails again. In all cases it fails with this error:Also it looks like the
tx()
method is creating a new transaction. Is this really the case ? For my implementation I need to use the Tinkerpop definedgraph.tx().commit()
I can't use the orient specificgraph.commit()
.In essence I would like to be able to do
Is there anyway to achieve this sort of behaviour using orientdb ?