You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for Dexie.js, this is really a nice way to use IndexedDB!
At the moment it's possible to exec an asynchronous action in the table hooks (for example with a promise). But if a hook modifies the object (obj), it is actually not persisted because when the object is later fetched it bears no trace of the modification.
Related to #14. There is a solution on its way. This is a limitation, yes! The change is a part of a larger change with a redesign of the internal chaining of filters to be asynchronic and then make the hooks take advantage of that.
You may modify the obj but in current version, that has to be done in the same call to have any effect.
Yes this is definitely a duplicate of #14. Maybe the title of #14 could be edited to reflect the generic nature of the limitation. This is why I've missed it when I checked for duplicates.
Hello,
First, thank you for Dexie.js, this is really a nice way to use IndexedDB!
At the moment it's possible to exec an asynchronous action in the table hooks (for example with a promise). But if a hook modifies the object (obj), it is actually not persisted because when the object is later fetched it bears no trace of the modification.
Could there be a way to tell to wait until the async action is finalized?
Maybe something like the following:
But it's not Promise-oriented at all :-(
Any ideas about it?
Thank you
The text was updated successfully, but these errors were encountered: