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
My application's domain logic is already in a web-worker; is the additional worker abstraction necessary in this case? Is there a trick to using absurd-sql in this manner? I'm unable to get it to start, as it gets stuck waiting at dist/indexeddb-backend.js:809, in the waitRead function of the Writer.
EDIT: Oh I see, starting to build my mental model of this thing. The indexeddb-backend wants a thread to itself for this very reason. In my case, I use ThreadsJS and they still don't seem to play nicely.
The text was updated successfully, but these errors were encountered:
My application's domain logic is already in a web-worker; is the additional worker abstraction necessary in this case? Is there a trick to using absurd-sql in this manner? I'm unable to get it to start, as it gets stuck waiting at dist/indexeddb-backend.js:809, in the waitRead function of the Writer.
EDIT: Oh I see, starting to build my mental model of this thing. The indexeddb-backend wants a thread to itself for this very reason. In my case, I use ThreadsJS and they still don't seem to play nicely.
The text was updated successfully, but these errors were encountered: