Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQL query with IN behaves in the same way as CONTAINS but does not use index. #7386

Closed
SafwanHak opened this issue May 3, 2017 · 2 comments
Assignees
Milestone

Comments

@SafwanHak
Copy link

OrientDB Version: 2.2.19

Java Version: 8

OS: Centos

Expected behavior

an EMBEDDEDLIST field can be queried with
tagged_users in "3333", should use the index whereas tagged_users contains "3333" works.

Actual behavior

does not use the index. either fix disallow the syntax "in" on embedded list or have it use the index.

Steps to reproduce

Create embeddedList field. add a non unique index on it.
run query "EXPLAIN select from table where embeddedField in "3333", it fails.
run query "EXPLAIN select from table where embeddedField in "3333", it works.

@tglman tglman added this to the 3.0.0 milestone Jan 2, 2018
@tglman
Copy link
Member

tglman commented Jan 2, 2018

Hi,

As far as I know this is fixed in 3.0

Regards

@luigidellaquila
Copy link
Member

This issue is no longer valid. In V 3.0 IN and CONTAINS have different (and correct) behaviors

Closing

Thanks

Luigi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants