The SQL Database storage that used to be in HTML 5 has been removed,
both from the HTML 5 spec and from the Web Storage spec that had been
defining it. It is still present in the current Working Draftof the
Web Storage spec from April 23rd:
http://www.w3.org/TR/webstorage/#sql
http://www.w3.org/TR/2009/WD-webstorage-20090423/#sql
But as you can see for yourself, it's gone in the current Editor's
Draft:
http://dev.w3.org/html5/webstorage/#sql
Which is not to say ol Hixie hasn't been known to change his mind
before. But until the vulnerabilities in this are well considered, I
wouldn't count on SQL coming back:
http://trivero.secdiscover.com/html5whitepaper.pdf
Also, I forgot to mention the related issue of offline mode for HTML 5
docs. Seems like you'll get almost everything you could want with a
cache manifest:
http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html
Joseph Holsten
Are you saying providing a local data store so web apps can work offline is a bad idea?
Because key/value is only the way to go for key/value data. Gmail's new iPhone/Android interface couldn't possibly work without a relational database.And yes, they really would all use sqlite3. They'd be insane not to. It's fast, small, public domain, supports transactions, has no external dependencies beyond C library functions and is already available for Win, OS X, and Linux. All the browsers need to build to spec is the bridge from JavaScript to sqlite3.
I think providing a nosql local store is a good idea.