I asked this on stackoverflow but I didn't get any response so I'll repeat
it here.
In orientdb 2.0.14, executing the statement:
db.traverse('in(\PM_child\')').from('#22:0').all().then(function (results) {});
would return all of the object contents along the path. However in 2.1.5 I
get the contents of #22:0, but only the @rids of the other traversed
objects.
Doing this as a raw query:
db.query('traverse in(\'PM_child\') from #22:0').then(function (results) {}
yields the same issue.
How do I get the same results from 2.1.5 that I was getting from 2.0.14?
I've been trying to do the same thing with select and fetch plans but it
returns way too much, expanding parts of the tree I don't need. All I want
is to return all vertex and properties in the tree following the requested
links.
I know how many links I have to traverse and even the vertex classes but
that is user programmable. I would have to construct the nested select
statement on the fly to accomplish this. Using traverse seems to be the
simplest way to let orientdb do the work for me.
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
