Open mustafa0x opened 3 months ago
Theoretically, you could proxy the web implementation and use whatever you want.
@mustafa0x
autosave
with default to false. Set this property to true when you set the jeep-sqlite component in your app, it will allow you to not care about the saveToStore and then fix the easy pitfall.Hope this clarify.
Thanks you so much @jepiqueau, I'm very grateful for the tremendous effort you've put into this very-useful plugin!
the large size is mainly due to the size of the sql-wasm.wasm
The jeep-sqlite stencil component alone is >500kb (the sql-wasm is 640kb.)
@mustafa0x see also my answer to issue#579
First, I want to thank the maintainer for the huge effort they've put into this incredibly valuable plugin.
Second, I want to ask: for web, is there an alternative to jeep-sqlite? I've noticed two issues with it:
saveToStore
after any changes. This creates an easy pitfall: the developer makes changes create/update/delete but forgets to callsaveToStore
.I suggest something like rhashimoto's IDBBatchAtomicVFS.