David Fahlander

> We had great improvements using @dfahlander 's approach on a tiny table of some few hundred records. Are you considering to change the implementation of `.anyof()` to use this...

You can store and index reversed versions of the strings you need to be searchable.

No

Given your table has an index '[AccountName+ProductEnterType]': ```ts await db .InventoryScans .where('[AccountName+ProductEnterType]') .anyOf([accName, 'SCAN'], [accName, 'MANUAL'], [accName, 'EXTDEVICE']) .toArray(); ```

I think indexeddbshim provides indexedDB on node. No, there's not been so much discussion about this but I'm also having ideas about making it possible to use Dexie towards other...

Hi, and thanks for your nice words. IndexedDB is still accesssed directly (outside DBCore) when opening a database. That code starts from Dexie.open() in dexie.ts under classes/dexie and the code...

I just closed #602 as it was an old thread. All that discussion originated from the state of the code before the typescript-rewrite. There is no current refactoring going on...

The best example would be to look how it's done in [virtual-index-middleware.ts](https://github.com/dfahlander/Dexie.js/blob/master/src/dbcore/virtual-index-middleware.ts). You need to return an object that corresponds to DBCoreCursor interface. If you're doing decryption of value but...

I cannot see any obvouis problem by looking at the code. Seems correct if decrypt() handles undefined and returns undefined without throwing. Have you tried what happens if you don't...

Maybe fakeIndexedDB will call onsuccess synchronously on events. This would make Dexie.waitFor() recursively call itself over and over. Suppose it's an easy fix in fakeIndexeddb if so.