If you think this isn’t a real problem in practice, watch this talk. This is something neither IndexedDB or WebSQL can provide until the Durable Storage API has shipped (and no browser currently has). the browser cannot start arbitrarily deleting data when disk space runs low.
(It depends on the use case, but see my database comparison tool for a demonstration of batch insert performance).Įven more saddening for the web platform as a whole is that, despite being blessed with no less than three storage engines (LocalStorage, WebSQL, and IndexedDB), many developers are still electing to go native for their storage needs. Secondly, although Safari’s “modern IndexedDB” rewrite has resolved many of its gnarliest bugs, their implementation is still around 50x slower (!) than WebSQL, even in the WebKit nightlies. That said, there is still good reason to doubt that web developers will be able to safely hop onto the IndexedDB bandwagon anytime soon, at least without fallbacks.įor one, it’s unclear when the fixes from WebKit will be released in Safari proper (and how soon we can stop worrying about old versions of Safari).
#WEBKIT NIGHTLIES ANDROID#
Thankfully, this WebSQL-as-polyfill practice is becoming less and less necessary, as pre-Kitkat Android slowly fades into memory, and Safari fixes its lingering IndexedDB issues. (See LocalForage, PouchDB, IndexedDBShim, and YDN-DB for popular examples of this.) Although the spec was deprecated over 5 years ago, it still lives on, mostly as a fallback from its more standards-friendly successor, IndexedDB. Try it out!įor better or worse, WebSQL is still a force to be reckoned with in web development. TL DR: I rewrote the Cordova SQLite Plugin it’s faster and better-tested.
0 kommentar(er)
