indexedDB is quite a low level in what the interface gives you. This includes what options you have available for querying (just accessing a key range, upper/l

indexedDB is quite a low level in what the interface gives you. This includes what options you have available for querying (just accessing a key range, upper/lower bound, forward or backwards (backwards can be much slower), rather than a full query language like SQL etc.. So you need to design your app / data format and pre-plan any queries so you'll have the indexes you need, or do some glue logic to combine indexes as needed.