Is there another way to access the $stack variable?

On Friday, January 23, 2015 at 3:06:43 PM UTC+2, john davids wrote:
>
> Hello,
>
> I was trying the same thing. I have a traverse query
>
> select $stack, $path from
>     (traverse ...)
>
> and the result is
>
> $stack
> $path
> [](#12:7)[](#12:7).out_Relation[0](#14:3).in(#12:6)[](#12:7).out_Relation
> [0](#14:3).in(#12:6).out_Relation[0](#14:2).in(#12:5)[](#12:7).out_
> Relation[0](#14:3).in(#12:6).out_Relation[0](#14:2).in(#12:5).out_Relation
> [0](#14:0).in(#12:4)[](#12:7).out_Relation[0](#14:3).in(#12:6).out_
> Relation[0](#14:2).in(#12:5).out_Relation[2](#14:7).in(#13:0)
> how come the $stack is empty? I was interested in parsing the last $path
>
> TY
>
> On Thursday, August 9, 2012 at 3:38:23 AM UTC+3, Lvc@ wrote:
>>
>> Hi,
>> you can access to the "$stack" variable ;-)
>>
>> Lvc@
>>
>> On 5 August 2012 00:34, mikkadar <[email protected]> wrote:
>>
>>> Hello,
>>>
>>> I am trying to retrieve all the paths that starts at a specified vertex 
>>> named vertexX using SQL traverse, and for that I am using the following 
>>> query:
>>>
>>> select $path from ( traverse V.out, E.in from ( select from V where name 
>>> = 'vertexX' ) )
>>>
>>> One of the returned path values that I get when I print out is:
>>>
>>>
>>> #6:17.out.#7:28.in.#6:13.out.#7:19.in.#6:10.out.#7:12.in.#6:15.out.#7:4.in.#6:19.out.#7:27.in.#6:5
>>>
>>> Intuitively, #6:17 is the RecordID of vertexX, and the RecordIDs that 
>>> include 6 are for vertices while those that include 7 are for edges.
>>>
>>> However, and without doing string manipulation, is there a 
>>> straightforward way to extract the vertices and the edges from the returned 
>>> path string?
>>>
>>> Thanks a lot.
>>>
>>> /Miky
>>>
>>> -- 
>>>  
>>>  
>>>  
>>>
>>
>>

-- 

--- 
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.

Reply via email to