W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2007

[whatwg] SQL API - SQLVersionChangeCallback vs SQLTransactionCallback

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 26 Oct 2007 22:36:55 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0710262225390.7001@hixie.dreamhostps.com>
On Thu, 25 Oct 2007, Dimitri Glazkov wrote:
> 
> I may be completely alone in this one, but is schema versioning as part 
> of the API really a necessary thing? I mean, it's convenient, but is it 
> necessary? Just trying to keep it simple.

In particular with the offline stuff, it is highly likely that code will 
be running and interacting with the database in one window when a script 
tries to update the schema, and we don't want authors to have to implement 
some primitive locking facility of their own to prevent old versions 
corrupting the data. I think it's relatively light-weight yet provides 
something that could end up being really useful in certain cases.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 26 October 2007 15:36:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:37 UTC