Closed zifnab87 closed 9 years ago
@lvca I updated the description because I thought class: notation support was forgotten for verticies but it seems that it is mandatory for them, while cannot be used with edges. Thanks
just making sure that this didn't slip by. Thanks
@zifnab87 I'd mark this issue as invalid, because the semantic of addVertex() and addEdge() is different. Check Blueprints JavaDocs. in addVertex the first param is the ID, in addEdge is the label. So the current behavior is correct.
About "addEdge with properties altogether" is not Blueprints, so you should call as OrientVertex, not Vertex.
Hi, In the documentation it is stated that we have to use class:className when we are creating both Vertices and Edges: http://www.orientechnologies.com/docs/2.0/orientdb.wiki/Graph-Database-Tinkerpop.html#create-element-and-properties-all-together http://www.orientechnologies.com/docs/2.0/orientdb.wiki/Graph-Database-Tinkerpop.html#transactions
I found that for a vertex this works
but this doesn't
and for an edge:
this works:
and this doesn't
When I add Edge with "class:" notation I get this warning and this exception
WARNING: Requested command 'Committing the active transaction to create the new type 'class%3ATestEdgeClass' as subclass of 'E'. The transaction will be reopen right after that. To avoid this behavior create the classes outside the transaction' must be executed outside active transaction: the transaction will be committed and reopen right after it. To avoid this behavior execute it outside a transaction Exception in thread "main" com.orientechnologies.orient.core.exception.OSchemaException: Invalid class name found. Character '%' cannot be used in class name
while when I add a Vertex with no "class:" notation I don't get a Warning and it is being added in V class
I am using
Could it be implemented in souch a way so that it is consistent for both Verticies and Edges?
Also it seems that addEdge with properties altogether ( in the mentioned documentation example) is not supported anymore since blueprints doesn't provide it? The documentation needs an update if that is the case.
Thank you!