David Fahlander

Thanks @hisem for posting how you solved the issue. I would though strongly advice against instantiating a new Dexie for every request. It would be very slow as it would...

This seems odd. I'm wondering if there's something else that fails and the transaction error would be just a secondary error. Is `id` a valid indexable key type and is...

* If criterias would have been type `equals`, you could use a [compound index](https://dexie.org/docs/Compound-Index) and use `where({billDate: x, billNo: y})`. * If all criterias but one criteria is of type...

The most straight-forward way for paging in Dexie is to use an offset()/limit() strategy. In case you want the result to be ordered by some other index than the queried...

Are you using moduleResolution "node" in tsconfig as suggested on the sample page? There might also be webpack- or typescript configuration causing problems with named imports. Please provide a link...

This is not a dexie error. The problem is that your own typescript code targets ES5 while you import a modern version of dexie targeting es2015 (which is wasn't available...

IndexedDB can enumerate indexes in ascending or descending order. To include several keys in one index, you can use [compound indexes with orderBy](https://dexie.org/docs/Compound-Index#using-with-orderby) but it is not possible to mix...

There are future plans for improving both ordering, querying and paging. Last year the focus has been reactivity and sync. Don't know exactly when Dexie will provide richer queries but...

Sorry for late reply. I wish I could answer these questions but I can only contribute with what I would believe based on my experiences with IndexedDB. If you need...

There's no geospatial indexing support in IndexedDB or in Dexie. You may use an index to search range in of the dimensions, and filter out the second dimension from that...