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
Hi, I'm new to the library, but I would really like to be able to use it in our environment for a lot of applications. It seems that the memory model is very limited. Could we not compile SQLite to Wasi so that it could take advantage of the filesystem from the host environment? SQL.js could provide a default host implementation that is just an array of memory like it is currently doing...or perhaps wasi just becomes another way to load like we have wasm and asm currently.
Is this feasible? My team might be able to do the work if this sounds like a good idea. I would love some feedback.
Unfortunately I can't even get SQL.js with asm.js to run in our environment even though it was just working about a week ago, I could really use some help here: #568
The text was updated successfully, but these errors were encountered:
Hi!
It's definitely possible to compile sqlite to wasi, but it's out of scope for sql.js. If you start your own project, I'd be happy to link to it in the readme here
Hi, I mean compiling sqlite to Wasi and having that binary as one of the officially supported in SQL.js. Is that out of scope? So you could import sql-wasm.js or sql-wasi.js.
Wouldn't this make SQL.js much more useful by allowing devs to hook into a filesystem for persistence?
Hi, I'm new to the library, but I would really like to be able to use it in our environment for a lot of applications. It seems that the memory model is very limited. Could we not compile SQLite to Wasi so that it could take advantage of the filesystem from the host environment? SQL.js could provide a default host implementation that is just an array of memory like it is currently doing...or perhaps wasi just becomes another way to load like we have wasm and asm currently.
Is this feasible? My team might be able to do the work if this sounds like a good idea. I would love some feedback.
Unfortunately I can't even get SQL.js with asm.js to run in our environment even though it was just working about a week ago, I could really use some help here: #568
The text was updated successfully, but these errors were encountered: