Show HN: NoSQL, but it's SQLite (opens in new tab)

The implementation is very clearly included, if you... scrolled down.

And the point is, you could easy do `const db = new Database("./database.sqlite")` instead.

The wrapper makes it so manipulating your database is just like manipulating a plain Javascript object.

Yes that is exactly what it is! It's basically a very small upgrade over my favorite database: A JSON-file :)

I'm using something like this for a small personal project that's only going to have a couple of users. Basically, just an app for myself and my girlfriend for all of the various restaurants, movies, recipes, tv shows, locations, etc. that we plan to go to/do at some point in the future. It's basically just a glorified todo list that uses APIs (TheMovieDataBase, OpenStreetMap, etc.) to grab additional metadata and images to present everything nicely

I want us both to be able to make notes/add ratings to each item, so the set of tables looks like this:

    - TodoItems
    - Notes
    - Ratings

Where every TodoItem can have multiple Ratings/Notes attached. Because each of the TodoItems is going to be of a different type with different metadata depending on the type of item (IMDB/TMDB id, image url, GPS location), and I want it to be extensible in future, its schema has ended up looking like this:

    CREATE TABLE TodoItems (
      id INTEGER PRIMARY KEY NOT NULL,
      kind TEXT NOT NULL,
      metadata BLOB NOT NULL
    );

With SQLite's json manipulation functions, it's actually pretty pleasant to work with. As it grows I might end up adding some indexes, but for now the performance seems like it will be fine for this very low traffic use case. And it makes deployment and backups incredibly simple.

Postgres added native support for JSON in 2012. People have been using RDBMS to store denormalized data and even as a key-value store for way longer than that. In fact, it's very hard not to do that

So it's a lot like the shelve builtin module?

Not sure what your exact use case is, I'm curious actually, but storing JSON strings should work much better. JSON functions are supported since SQL Server 2016 [0]. This is how I do it atm. I store only indexible content in table columns and everything else goes into an `attributes` JSON column. MSSQL supports indexes even on JSON fields, but I have not tried that, yet.

0 - https://learn.microsoft.com/en-us/sql/relational-databases/j...

This needs some explanation

Submitted it to The Daily WTF yet?

Users flagged it. We can only guess why users flag things, but there are usually clues in the comments. I've turned the flags off now.

p.s. @dang doesn't work - you have to email hn@ycombinator.com if you want mostly-guaranteed message delivery.

Maybe because it’s written with a LLM