SQLToy VS sql.js

You might look at SQLToy which is a DB and blog I wrote to teach how SQL processing works internally: https://github.com/weinberg/SQLToy

I am a Javascript developer and I've used SQL for years but it's always been a bit of a black box. I recently learned about the SQL order of operations and the relational model and it kind of blew my mind. In the process of digesting this information I wrote my own database in Javascript which I think might help others in my same situation. The result is SQLToy.

It is a SQL database written in Javascript. It's under 500 lines of code (including comments) and has zero dependencies.

The purpose of SQLToy is not to use it as a database but to learn SQL. Instead of doing this from the "outside-in" by learning the query language you do it "inside-out" by going through the implementation of the most common SQL operators. Instead of just learning what the operators do, you also learn how they do it which (hopefully!) should lead to a much deeper level of understanding.

A detailed wiki walks through the code of 15 different SQL operations including SELECT, WHERE, JOINs, GROUP BY, Aggregate Functions COUNT, AVG, MAX, MIN to name a few.

The wiki can be found here: https://github.com/weinberg/SQLToy/wiki

Feedback appreciated!

Hi HN! A friend and I were inspired by projects like https://github.com/sql-js/sql.js and the idea of querying files served over CDN with HTTP range requests. We started thinking: what would a database that was specifically designed for this type of use case look like? So we started building one, and we landed on a functional prototype that we're pretty proud of!

With our prototype, Appendable, we're able to serve and query large (GB+) datasets by hosting them on a static file host like Amazon S3 or Cloudflare R2 without running a separate server and worrying about things like tail latency, replication, and connection pooling -- all that is handled for us by the file hoster.

Additionally, one tenet that we have been following is Appendable won't touch your underlying data, so your jsonl file is preserved and we point at that data instead of consuming it into an Appendable-specific file format. This keeps your data yours and makes it easy to introspect the data: just open it up with your favorite editor aka vim.

We're curious what you think, we're excited to build this out further to get the performance even better and add features like pubsub. Everything is open source at https://github.com/kevmo314/appendable.

Kevin and Matthew

My project is powered by sql.js, I recommend checking that out if you're interested - https://github.com/sql-js/sql.js/

Maybe you can try to use some SQL database compiled as Web Assembly Modules? Like this one for example: https://github.com/sql-js/sql.js

If you want to have persistence, then I would go with a database like Dexie, as it uses IndexedDB and has transactions. If you just want something that's in memory, you could look at Sql.js or something simple like lowdb.

not necessarily. you can host an html/js/sqlite site on github pages for free. json -> sqlite3 js -> sql

Link: https://sql.js.org

Does it work with really large files? Like, >100mb or so. I was considering making something similar but with sqlite.js [1], but the problem with it is that it loads everything in memory, so I wasn't entirely sure how it will deal with larger workloads.

[1]: https://sql.js.org/#/