orientechnologies
Add support for uuid / tree based RIDBag
From @phpnode on April 2, 2014 21:37
Currently only the simpler 'embedded' RIDBag type is supported. We need to also support the tree based type.
Copied from original issue: codemix/oriento#5
From @dmarcelino on December 29, 2014 11:39
Hi @phpnode, I believe I've just stumbled upon this issue / issue #129. When I run a query such as db.select().from('Person').fetch('out_Eat:1 out_Eat.in:2') the linked vertices come as RIDs. Essentially I seem to be unable to use Fetch Plan with level 2. Is this a manifestation of issue #5? I've pushed a test so you can take a look at my particular case scenario. Thanks.
From @dmarcelino on December 29, 2014 16:21
This is a bit more intriguing than I initially thought, when the query with fetch plan depth 2 returns one record it works as expected. The issue only manifests when the resultset has more than one record, as demonstrated by my latest commit.
From @dmarcelino on January 7, 2015 15:25
@phpnode, please disregard the tests I've added concerning this issue. They are a separate issue covered by #186. Cheers
Related to https://github.com/orientechnologies/orientdb/issues/5679
Hi I was curious if there is a script available for turning the 'embedded' response into a tree on the client side. I have been having a hard time constructing one that can account for the variations in response structure between query types e.g. Traverse vs Selects and Breadth vs Depth first and figured I would ask in case i'm doing work I don't need to. Thank you.
It will be supported in protocol V37
https://github.com/orientechnologies/orientjs/issues/251
