No I think it's a bug. I played a bit more with the query and discovered
this:
Query as I posted above produces result with a console error:
orientdb {db=Customers}> SELECT FROM Year LET $account = (SELECT FROM #249:0)
WHERE value = 2017 AND account = $account[0].@rid
+----+------+------+-----+-------+
|# |@RID |@CLASS|value|account|
+----+------+------+-----+-------+
|0 |#265:0|Year |2017 |#249:0 |
+----+------+------+-----+-------+
However, the same query with just switched positions of the filter elements
in the WHERE clause produces no result and no console error either:
orientdb {db=Tetraop}> SELECT FROM Year LET $account = (SELECT FROM #249:0)
WHERE account = $account[0].@rid and value = 2017
0 item(s) found. Query executed in 0.002 sec(s).
Shall I log it as a bug?
On Friday, January 27, 2017 at 11:55:00 AM UTC-8, Borov wrote:
>
> Any idea anybody?
>
>
> On Thursday, January 26, 2017 at 8:20:16 AM UTC-8, Borov wrote:
>>
>> Sorry, forgot to mention the version. It's the latest at the moment 2.2.15
>>
>> Thanks,
>>
>> On Wednesday, January 25, 2017 at 11:21:33 PM UTC-8, [email protected]
>> wrote:
>>>
>>> Hi Borov,
>>>
>>> which version are you using?
>>>
>>> Thx.
>>>
>>> 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.
