Unfortunately they chose a set of APIs that is strictly weaker than what we have access to via WebSql. When I port from WebSql to IndexDb, I will need to imple

Unfortunately they chose a set of APIs that is strictly weaker than what we have access to via WebSql. When I port from WebSql to IndexDb, I will need to implement in Javascript a bunch of things that sqlite3 is already doing for me in C. I actually started out with a very NoSQL-like architecture on top of WebSql that's closer to the IndexDb model. But when I started taking more advantage of sqlite3 to do the heavy lifting (joins, nested subqueries, etc) I got an order of magnitude better performance. Switching to IndexDb means going back to the slow way.