4 ms·
WebSQL was a completely separate debate, if I recall correctly, the issues there had to do with WebSQL being heavily dependent on SQLite, a single implementatio
by azakai 13y ago
WebSQL was a completely separate debate, if I recall correctly, the issues there had to do with WebSQL being heavily dependent on SQLite, a single implementation. So it was hard to spec in a vendor-independent way like web standards require.
IndexedDB is much less capable than SQLite, no doubt about it, but still very useful, and far far simpler and feasible to spec and standardize (which it has been).
- Touche 13y agoIn what way is it less capable?
- azakai 13y agoSQLite supports a pretty comprehensive query language including joins, sorts, filtering, etc etc. It's a full RDBMS.
- dgregd 13y agoIt is another case where they make fundamentally bad decision. In case of WebSQL, 40 years of legacy is not important. Millions business apps developers needs are not important. Clean and nice spec is more important for Mozilla guys. However in case of Brendan Eich baby, legacy is very important. Ugly hacks like asm.js, without W3 specs, are promoted. Try to guess why.
- iso-8859-1 13y agoBut SQL is already standardized! They just have to determine a reasonable subset of the existing standard.
- azakai 13y agoSQLite is not identical to any of the SQL standards. For example it is typeless http://www.sqlite.org/datatypes.html http://www.sqlite.org/datatypes.html which is different than most RDBMSes.