W3C home > Mailing lists > Public > public-html@w3.org > February 2008

ISSUE-36 (client-side-storage-sql): Client side database storage SQL statement support [HTML 5 spec]

From: HTML Issue Tracking Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 19 Feb 2008 18:55:30 +0000 (GMT)
To: public-html@w3.org
Message-Id: <20080219185530.8FA636B62B@kent.w3.org>

ISSUE-36 (client-side-storage-sql): Client side database storage SQL statement support [HTML 5 spec]

http://www.w3.org/html/wg/tracker/issues/

Raised by: Shawn Medero
On product: HTML 5 spec

Should the client-side database storage section of the specification clearly outline what SQL statements _must_ be supported by implementors?

If so what are the MUSTs vs. SHOULDs?

Raised by Mikko Honkala via email:
http://lists.w3.org/Archives/Public/public-html/2008Feb/0288.html

> The current spec only notes: "Note: A future version of this
> specification will probably define the exact SQL subset required in more
> detail".
> http://tinyurl.com/23d324

> This is not a good position, especially since implementations are
> starting to pop up. On a high level, we need requirements and further
> proposals for the subset that is going to get specified as a MUST level
> requirement in the spec.

## Proposals

Mikko Honkala suggested:
http://lists.w3.org/Archives/Public/public-html/2008Feb/0288.html

> My kick-off proposal would be to start with the number 3 : "The SQL
> subset supported by SQLite", combined with their support for full - text
> search:
> http://code.google.com/apis/gears/api_database.html#sqlite_fts
> http://www.sqlite.org/cvstrac/wiki?p=FtsTwo
> 
> And making BEGIN/COMMIT/ROLLBACK  no-ops, since transactions are
> built-in to the API.
Received on Tuesday, 19 February 2008 18:55:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:12 GMT