Hi Luca,

Thanks for the reply!

However, it gives the same result. No traversing! Even fetchplan *:-1 
doesnt help. Is another code path in OrientDB being followed when calling a 
batch instead of a command via REST?


Martin

On Wednesday, August 13, 2014 5:30:21 PM UTC+2, Lvc@ wrote:
>
> Hi Martin,
> fetchplan goes after the WHERE. Try this:
>
> select from comment where @rid=#13:11 fetchplan Replies:1000
>
> About the console command:
>
> export record json
>
> It's totally unrelated to the select before. Try using fetchplan (also) on 
> "export record" command:
>
> export record json fetchPlan:Replies:1000
>
> Lvc@
>
>
>
> On 13 August 2014 16:05, Martin Bean <[email protected] <javascript:>> wrote:
>
>> Funny thing is, when I execute the following in the console:
>>
>> select from comment fetchplan Replies:1000 where @rid=#13:11; export 
>> record json
>>
>> I also get:
>>
>> {
>>     "result": [
>>         {
>>             "@type": "d",
>>             "@rid": "#13:11",
>>             "@version": 2,
>>             "@class": "Comment",
>>             "EditText": "main comment",
>>             "Replies": [
>>                  "#13:1",
>>                 "#13:3",
>>                 "#13:4",
>>                 "#13:5",
>>                 "#13:10"
>>              ]
>>         }
>>     ]
>> }
>>
>> Its not traversing...
>>
>> -- 
>>
>> --- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

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