So I haven't found a good solution to this, as of now I'm making this query:
SELECT *, out('hasEdge') as first_vertexes, out('hasEdge').out('hasEdge') as
second_vertexes FROM #11:1 FETCHPLAN first_vertexes:1 second_vertexes:1
and in the resulting rows that I get I manually match the the in's and the
out's @rids for the first and second vertexes and building the nested
object before sending it in the json response.
Seems like there must be a better way but I can't have this be a blocker
for me so... temporary solution until someone can figure something else out.
Cheers,
Eric
On Monday, September 7, 2015 at 10:03:16 AM UTC-7, Eric Lin wrote:
>
> Hi Michela,
>
> Trying that out in Orient Studio, it's still only retrieving nodes 1 level
> deep / 1 step away, it's not getting the vertexes two steps away and it's
> also not returning properties of the adjacent vertexes it's only returning
> the @rid's... :(
>
> However, I have noticed in Orient Studio in the PROPERTIES column it only
> shows the @rids but in the OUT column it shows nested objects which means
> that they must have been pre-fetched ? But we're just not attaching those
> prefetched results to our PROPERTIES?
>
> Thanks for all the help,
> Eric
>
> On Monday, September 7, 2015 at 1:31:05 AM UTC-7, [email protected]
> wrote:
>>
>> Hi Eric,
>>
>> Sorry my bad :)
>>
>> Try this:
>>
>> SELECT *, out('hasEdge') as FirstEdge FROM #12:0 FETCHPLAN FirstEdge:-1
>> *:-1
>>
>> Regards,
>> Michela
>>
>
--
---
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.
