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?
> 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 :-)
AndrewSChapman|3 years ago
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.
mr_toad|3 years ago
If only. It’s much closer to DBM than it is to Mongo.
azangru|3 years ago
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 :-)
actionfromafar|3 years ago
IndexedDB seems like a whole bag of gotchas. SQLite + simpler browser provided file backing seems interesting to me.
simonw|3 years ago
Think Redis vs PostgreSQL.