Dexie 3 introduced some breaking changes.
Mainly, it changes how DB migrations are handled:
Each version should contain the full schema, not just the changes to the last one
Unless there is an upgrade(), you can safely remove older versions from your code now
Also, there are some changes to how querying works, which are adjusted to in this PR.
This also introduces tests for the migration functionality, as well as for the different query types.
Finally, you can now also set _shouldLogQuery = true on the indexed-db service to make it output which index is used for a given query. This can be used to optimize your schema.
This PR also updates documentation accordingly (and moves to ES6 syntax everywhere).
See: https://github.com/dfahlander/Dexie.js/releases/tag/v3.0.0
Dexie 3 introduced some breaking changes. Mainly, it changes how DB migrations are handled:
upgrade(), you can safely remove older versions from your code nowAlso, there are some changes to how querying works, which are adjusted to in this PR. This also introduces tests for the migration functionality, as well as for the different query types.
Finally, you can now also set
_shouldLogQuery = trueon the indexed-db service to make it output which index is used for a given query. This can be used to optimize your schema.This PR also updates documentation accordingly (and moves to ES6 syntax everywhere).