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, 24 Oct 2007 23:09:20 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0710242303040.10579@hixie.dreamhostps.com>
On Wed, 24 Oct 2007, Brady Eidson wrote:
>
> First off, my first impression of the new API is that I like it a lot 
> and think it addresses most - if not all - of the outstanding issues.

Great!


> We'll see if that impression continues after I process it all!  =D

Please send feedback if it doesn't! :-)


> The database name is - and should remain - a technical detail that is 
> internal to the implementation of a web application.  I propose we 
> provide an optional way for an openDatabase() call to include a 
> DatabaseDescription, which is meant to be a human-readable name or 
> description of the database.  This would make policy prompts regarding 
> the database (creation, increasing the size) as well as the management 
> UI potentially more meaningful and clear to the user.

Done.


> A side proprosal that might help consolidate the "should I allow this 
> database to be created?" and "should this origin be allowed to go over 
> its size limit?" prompts would be to provide another optional argument 
> to the openDatabase() call which is the "expected size of the database" 
> which is something many application developers may be able to establish 
> ahead of time.

Done.

We might drop estimatedSize if it's rarely used appropriately (e.g. if 
people always say "0" or "999999999999999999999").

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

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