Problem with SQl Where IN clause and subselect

[EricSchreiner]

OrientDB Version: 3.0.14

Java Version: 1.8.x

OS: Windows

Expected behavior

See attached Screenshot from Orientdb studio

Actual behavior

See attached Screenshot from Orientdb studio

Steps to reproduce

See attached Screenshot from Orientdb studio

[luigidellaquila]

Hi @EricSchreiner

The first query doesn't work because you are matching a key with a pair key, rid.
If you change it as follows it will work fine

SELECT key, rid from index... where key in (select key from index...)

Thanks

Luigi

[EricSchreiner]

Hi @luigidellaquila
(I would reopen but it seems I'm not allowed to.) I've tried a lot of different solutions but it seems to be a bug. See Screenshot below with your suggestion....

[luigidellaquila]

Hi @EricSchreiner

I tried it with DemoDB on v 3.0.14 and it seems to work fine, maybe it's already fixed. Could you please try your dataset on latest stable?

Thanks

Luigi

[EricSchreiner]

Hi @luigidellaquila my example was already running on 3.0.14

[EricSchreiner]

Hi @luigidellaquila
for you information: It works fine when i use a static list of keys in the IN clause instead of a select....

[luigidellaquila]

Hi @EricSchreiner

Can you please give me more details on how to reproduce?
I tried the following on DemoDB and the result is as expected

select from index:Countries.Id where key in (select key from index:Countries.Id where key = 1)

What is different in your case?

Thanks

Luigi

[EricSchreiner]

Hi @luigidellaquila ,
my key is OType.STRING and duplicates are allowed (INDEX_TYPE.NOTUNIQUE)

[luigidellaquila]

Hi @EricSchreiner

Thank you very much, I managed to reproduce the problem. I'll try to fix it ASAP

I'll keep you updated

Thanks

Luigi

[EricSchreiner]

HI @luigidellaquila
thanks....

[luigidellaquila]

Hi @EricSchreiner

I just pushed a fix, it will be in the snapshot in a few minutes and will be released with v 3.0.15

Thanks

Luigi

[EricSchreiner]

Hi @luigidellaquila
thanks....