Despite the fact that there is a lot of good stuff in html5, one thing I don’t get is a backup storage mechanism, first there is localstorage and sessionstorage, which are key value stores, one for one application instance ("one tab"). and the other works for all instances of this application so that they can exchange data. Both are saved when you close your browser and have a limited size (usually 5 MB), which is great and everything will be fine if we stay there.
But then there is the "Web SQL Database", which has the same security system as localstorage, the same size as everything, except that it works like sqlite, with tables and sql syntax and all that.
And bummer, it doesn’t work on the same data at all! These are not two ways to access your data, these are really two repositories for each html 5 application (not created by default, yes, but still you see my point).
What would I like to know if there is a reason why both of these mechanisms exist simultaneously? Or did they just look at the sql and nosql movement to select the best, and then go "twist it to add both!"? Why not implement local / session storage as a table inside web sql db?
azera source share