mike_r_parsons

You can already do this ... https://sql.js.org/#/?id=api-documentation:~:text=//%20You%2...

Is this (size) an issue in the real world?

I really don't know what problem(s) this solves. Don't all the javascript runtimes already have wasm engines built into the runtimes?

How does this compare to the following?

create table testInt(num Integer); WITH n(n) AS(SELECT 1 UNION ALL SELECT n+1 FROM n WHERE n < 1000000) insert into testInt select n from n;

On my machine - Mac Mini 3 GHz Dual-Core Intel Core i7 16 GB 1600 MHz DDR3

this takes Run Time: real 0.362 user 0.357236 sys 0.004530

30 network requests and 13 script requests to display some text on a page??? Surely this is not the most efficient way to do this???

This is awesome!

How big is the sqlite database you are using? Here is a similar project you might be interested in. https://datasette.io/

websocketd - Turn any command that uses stdin into a web socket server (i.e. connect to it from any browser) https://github.com/joewalnes/websocketd

sqlite shell - https://www.sqlite.org/download.html

combine the two for a high throughput web app - https://hackernoon.com/stream-a-million-websocket-sql-reques...

http://nodeca.github.io/pako/ http://pieroxy.net/blog/pages/lz-string/index.html

Don't get mislead by the "lite" in sqlite. I can do about 200k sql requests per second with a sqlite inmemory db and node.js