db.on('error') event is not available

[scazzy]

I'm trying to fix the DatabaseClosedError (db con closes randomly), and wanting to add a global handler for the same.

I tried adding db.on('error', handler), but it throws error. There's no 'error' event to subscribe to.

Using Dexie 2.0.3 via npm. Also tried with upgraded version.

Also, if you've a better solution for handling randomly closing db connection, would be helpful.
LocalForage and PouchDB handles these internally, but guess Dexie doesn't yet. If you can point out where to change, I can help with a PR as well.

[dfahlander]

It's obsolete since version 2.0: https://dexie.org/docs/Deprecations#dexieonerror--dbonerror

I've not seen there have been any problem with randomly closed database connections in IndexedDB. Though, if another Dexie instance is upgrading the version, all existing Dexie instances will close unless overriding the versionchange event to capture that and close/repopen the db from there.

[scazzy]

So the DB connection seem to close when app is open for long, maybe went on sleep and re-opened. We've noticed this often, primarily for long sessions.

There were issues reported on other libs as well, eg
tutao/tutanota#452
localForage/localForage#581
localForage/localForage#694

[dfahlander]

Ok. I see there's a reference to #613 also there. It would be nice to get an understanding of how to detect this state and solve it under the hood in dexie. Maybe look into how it is fixed in pouchdb and do something similar in Table._trans - which is the method that all calls will go through.

[adamJLev]

Also dealing with this issue, basically eventually if the page is open long enough DatabaseClosedError happens and any subsequent Dexie queyring after that stops working. This is on the latest Chrome and its been happening for a long time ( at least a year, basically since the beginning of my app), based on my Sentry JS exception logs.

But all that needs to happen is call db.open() to fix that, so I am also looking to put this in a central place.
Ideally Dexie handles this transparently, but for now I'll add a workaround.