sql - Duplicated edges with the same @rid in OrientDB -
i've discovered strange behaviour when querying edge class using orientdb (community-2.1-rc5). database returning exact same edge exact same @rid , exact same data, twice. instinct says bug...
this query
select e @class='likes' , (out in [#12:0,#12:221]) , in=#36:1913
and orientdb studio returns
http://s29.postimg.org/hwruv0zif/captura.png
this makes no sense. if go vertex , query likes relationship returns 1 registry... faced problem this?
this database i'm using if helps
https://www.dropbox.com/sh/pkm28cfer1pwpqb/aaavgel1eftogr4o0todtiaha?dl=0
to bug, should make request join google group. stackoverflow not best place kind of bug.
the problem somehow duplicated edge mistake. orientdb let unknown reason.
here bug discussion on orientdb google group : https://groups.google.com/forum/#!topic/orient-database/car7yujczci
in discussion luca(creator of orientdb) says :
"the problem without transaction creation of edge dirty. orientdb tries fix dirty reference, maybe that's reason why next time exception raised. i've changed default behavior of sql commands against graphs transactional"
upgrading recent version of orientdb ideal. maybe bug has been fixed.
Comments
Post a Comment