Hi,
I've attached the database export, including the defined index. And here's
the query:
SELECT @rid FROM User WHERE state="active" AND birthdayYear <= 1994 AND
birthdayYear >= 1958 AND ageMin <= 59 AND ageMax >= 59 AND height <= 176
AND height >= 161 AND heightMin <= 188 AND heightMax >= 188
Hi,
A small sample database and the query you execute will be enough
Thanks
Luigi
2015-03-05 21:18 GMT+01:00 Máté Gábri :
> Hi Luigi,
>
> sorry I'm new to this so please forgive my noob question. What should I
> provide so that you can test it? My code (nodejs) I'm using for testing, or
> som
Hi Luigi,
sorry I'm new to this so please forgive my noob question. What should I
provide so that you can test it? My code (nodejs) I'm using for testing, or
some test data with the query and index I'm using?
Best regards,
Mate
On Thursday, March 5, 2015 at 10:51:26 AM UTC+1, Luigi Dell'Aquila
Hi Mate,
there are no limitations in the number of properties that can be indexed,
so there must be a bug somewhere.
Could you provide a test case to reproduce it?
Thanks
Luigi
2015-03-04 22:25 GMT+01:00 Máté Gábri :
> Hi,
>
> I'm trying to get familiar with OrientDB's indexing to make some
>
Hi,
I'm trying to get familiar with OrientDB's indexing to make some
performance tests. I'm running a query on a class which uses 10+ conditions
in the WHERE statement with range selections, constants and IN conditions.
I've created the compound index in the same order as the fields appear in
