Hacker News new | ask | show | jobs
by wargames 1252 days ago
I haven't used IndexedDB in a while.. but my recollection is that it is basically SQLite. Not sure I see the advantage of this above and beyond what IndexedDB is already providing. What are the pros and cons of each approach?
4 comments

IndexDb is not a relational data store. It's much closer to Mongo than it it to Sqlite.

If you want relational tables, joins, aggregations etc, you want something like this (or the original Web SQL that was deprecated).

There is definitely a use case for it.

> It's much closer to Mongo than it it to Sqlite.

If only. It’s much closer to DBM than it is to Mongo.

> but my recollection is that it is basically SQLite.

SQLite, which has a SQL database engine, is, by definition, a relational database. IndexedDB is a non-relational, or noSQL, database. One can't be basically the same as the other :-)

https://nolanlawson.com/2021/08/22/speeding-up-indexeddb-rea...

IndexedDB seems like a whole bag of gotchas. SQLite + simpler browser provided file backing seems interesting to me.

One is a key value store, the other is a full relational database.

Think Redis vs PostgreSQL.