Similarly for the WebSQL apologists, there's no reason <50kb of JavaScript couldn't provide a fully featured SQL engine on top of IndexedDB - IndexedDB implements most of the hard work (indexes, transactions, the container itself) already.
No. To use your terminolgy, IndexedDB is like jQuery on top of LevelDB. We need just LevelDB without the IndexedDB overhead. Surprisingly, there are things you can do with LevelDB that you can't do with IndexedDB. It's too high a level of abstraction.
Could you point me to such a simple JavaScript library? When IndexedDB was anointed that was the argument -- that the benefits of WebSQL could simply be layered atop. So where is it?
IDB in Chrome may have LevelDB somewhere underneath but it lacks points 9,10,11,12. As far as I know it does not yet have true MVCC, no real concurrency for multiple readers and writers. Single-transaction-at-a-time. Readers block readers.
1. Embedding of LevelDB or Kyoto. BitCask is terrific but has too slow a startup time for large data sets.
2. No range support.
3. No IndexedDB-style gargantuan-spec and setVersion versioning complexity. No versioning at all.
4. Just humble powerful KV.
5. Node-style callbacks.
6. Get/set/unset.
7. UTF8 keys.
8. ArrayBuffer byte-array values only - developers can layer any slow serialization/deserialization abstraction else on top.
9. Unlimited storage quota when requested by the app.
10. An option for the user to see how much storage the app is using so they can uninstall if it uses too much for their liking.
11. Fast.
12. True MVCC auto-completing read/write transactions (readers block writers in most IDB implementations, not MVCC) or cross-tab in-memory lock api.
After that we need an async BTree api.