database.remove() doesn't remove IndexedDB local documents

[ofekd]

Case

Bug

Issue

GraphQL replication tried pulling new documents even after I ran db.remove(). Using the storage inspector in Firefox I could see the pull checkpoints were still there. I also suspect other local documents remain, but didn't have time to test.

In most browsers I can use IndexedDB.databases() to enumerate and delete them all manually. Does anyone know of a workaround for Firefox?

Info

• RxDB Version: 10.0.2
• Environment: Browser
• Adapter: IndexedDB
• Stack: Typescript, Babel, Vue

[pubkey]

Thank you for reporting. Fixed in the attached commit.

[ofekd]

Thank you for fixing, much appreciated

[ofekd]

I have installed 10.0.3 and the pull checkpoint still persists after remove().

Is there a way to get the list of the pouch IndexedDB databases? I would like to erase everything, regardless of remove().

[pubkey]

I am not sure how to get all indexeddb databases.
Can you make a PR with a test to reproduce the problem?
In the new release we remove the whole local document store, so I do not see any way how the checkpoint can still persist.

[ofekd]

I see in the storage explorer that RxDB created IndexedDB databases for both version 0 and version 1 of my schema (currently set to version 1 in the schema file). Is that intentional? I think it has something to do with it because the graphql pull checkpoint is set in the version 0 database. This was a fresh DB so it's not something that carried from old data.

[pubkey]

RxDB since version 10 creates a separate IndexedDB for local documents and 'normal' documents.
The local documents indexeddb always has version 0.

[ofekd]

I've added a failing test