Hi,
We have an ARTICLE -> SUPPLIER -> COUNTRY database, with loads of ARTICLE
records, quite a few SUPPLIER records and some COUNTRY records.
Now if we want to filter on articles with a supplier in a certain country
we can do this fast enough by querying like this:
select from (select expand(in('ARTICLE_SUPP_NR')) from (select
expand(in('SUPP_COUNTRY')) from COUNTRY where _id = 'NL'))
But if we want to filter on the ARTICLE table, or count something, things
get slow as there are a lot of results (about 80K) and it looks like
orientdb is not using any index created on the ARTICLE table.
Question is, can orientdb be quering in a way that indexes are used on a
subquery result? So my subquery would result in a bunch of expanded ARTICLE
rows, could filtering/sorting/counting on that result be executed on an
index somehow, so we still get good performance?
Thanks,
Wouter
--
---
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.
