It appears that this affects out() as a method, rather than as a function.
Here is a basic schema that illustrates the issue:
create class A extends V
create class B extends V
create class AB extends E
create class C extends V
create class D extends V
create class BC extends E
create class BD extends E
create vertex A
create vertex B
create vertex C
create edge AB from (select from A) to (select from B)
create edge BC from (select from B) to (select from C)
---
in the 3 vertexes, A, B, and C
This statement works:
select expand(out('AB').out('BC', 'BD')) from A
But this does not:
select expand(out('AB').out('BD', 'BC')) from A
The only difference is the order of the edges BC and BD. In the second one,
I should still expect to return the BC edge result, no?
Thanks
On Monday, 20 July 2015 16:26:57 UTC-4, valerio tarenghi wrote:
>
> Hi Bob
>
> Can you send your schema?
>
> thanks
> Valerio
>
> Il giorno lunedì 20 luglio 2015 22:08:25 UTC+2, BobJones ha scritto:
>>
>> Hi,
>>
>>
>> I am noticing that when I run a query such as select
>> expand(out('EDGE_NAME').out('EDGE_A', 'EDGE_B')) from x where y,
>>
>>
>> that the order of EDGE_A and EDGE_B inside the out() function matters. It
>> appears that if EDGE_A is found, the query will return results if EDGE_A is
>> the first name in the second out as in the example. But, if EDGE_B is
>> present, and EDGE_A is not, then no results will be returned?
>>
>>
>> Should not both be returned regardless of order?
>>
>>
>> Note, that I'm noticing this only on the second OUT()
>>
>>
>> Can anyone explain this behaviour?
>>
>
--
---
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.
