"Covered" fields in an index

First, does ODB (2.2 or 3.0) optimize to read only an index if all of the fields in the projection are contained in the index (i.e. if there’s no need to even read the actual record?

Many other databases support the idea of “extra” fields in an index; fields that are not actually part of the index itself, but are contained there to allow the server to fulfill the query without needing to read the actual record.

Any plans for ODB to support this concept?

Hi @eric24

For now, the indexes do not support extra fields and we have no specific plans to support them.
In some specific cases (eg. count(*)) OrientDB can avoid to load records, but in general it is not the case