Hey All,
I just noticed that an editor at the w3c seems to have hit a wall with
browser implementers,
as they are all using Sqlite as their backend database, and so there is
no second, independent implementation. (required for the standards process).
At some point, these specs will be used more on the server-side.
Currently, server-side packages are likely to use Sqlite as well.
So, at some point, when the stars align, someone may drudge through
a few w3c specs and create a contrib for "web sql".
An "enterprise" distribution of Chromium or Firefox would
be better off using PostgreSQL as its back-end, over Sqlite.
So, at some point, when the sales align, someone will have
financial incentive to deploy a "web sql" contrib module.
Here's a set of relevant w3c specs:
Simple async sql sub-set (the spec in trouble):
http://dev.w3.org/html5/webdatabase/
Typed arrays and casting (standard names)
https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/TypedArray-spec.html
It's fairly close to what's available now in postgres c libs;
COPY style / blob support (just solidified in the latest browser releases):
http://www.w3.org/TR/FileAPI/ <http://www.w3.org/TR/IndexedDB/>
http://www.w3.org/TR/2010/WD-file-writer-api-20101026/
For C++ fans, Object Oriented Sugar (not implemented / used yet) :
http://www.w3.org/TR/IndexedDB/
