- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 18 Oct 2007 01:29:56 +0000 (UTC)
On Fri, 12 Oct 2007, Anne van Kesteren wrote: > > I think there should be an error code for the database being full. For > some platforms there's not much storage space available and knowing > whether or not there's some space left is useful. So you can decide to > only store the critical data for instance. Added. On Fri, 12 Oct 2007, Scott Hess wrote: > > My counter-argument to this is that by the time you get the "database > is full" error, you're probably already sunk. Granted, but at least with an error code you'll know why you're sunk. :-) > I think what you're really asking for, above, is a means of saying "How > much data can I store?", so that you can make decisions about what to > store. In the limit, that's hard for the browser to guarantee, of > course. I think such an API would be best kept for v2 -- let's see if people care, first. On Sun, 14 Oct 2007, Scott Hess wrote: > > I think this does imply an ability to delete the entire local database, > which might be a reasonable API addition. Even short of this case, you > could also consider the named databases as part of an app's database > schema in the sense that data could be partitioned between named > databases, and later the partitioning could change, implying the need to > delete the now-unused databases. True. I've added "deleting databases" to a list of v2 feature requests, but maybe we should bring this one forward to v1. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 17 October 2007 18:29:56 UTC