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

[whatwg] SQL API and database metadata at creation

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 31 Oct 2007 23:05:00 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0710312304060.27205@hixie.dreamhostps.com>
On Wed, 31 Oct 2007, Scott Hess wrote:
> 
> One quibble I have with this revised aspect of the spec is that database 
> use somewhat overlaps schema.  A site can decide to have a single 
> database with many tables, or they can decide to divide their tables 
> across multiple databases, thus leading to three or four prompts.  
> There might be byzantine reasons for this - maybe a product is composed 
> of elements from three or four groups within a company, rather than 
> being monolithic, and the databases are used for namespace control.
> 
> Unfortunately, I can't think of a good action item WRT the spec.  I 
> suspect that the user-agent might end up going in the direction of 
> maintaining an aggregate quota for an origin.

I agree, but like you I don't know exactly what to say about this. This is 
an area where implementation experience will help. It may be, for 
instance, that nobody uses more than one database per app, and a prompt 
ends up being fine.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 31 October 2007 16:05:00 UTC

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