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

[whatwg] database full error (was: Re: executeSql API issynchronous)

From: Scott Hess <shess@google.com>
Date: Sun, 14 Oct 2007 15:57:50 -0700
Message-ID: <696e4b7c0710141557p68ecbb91yfa19a1fbca953f3c@mail.gmail.com>
In a transactional database system, it's entirely possible that once
you're out of space, you cannot drop tables or delete rows, because
doing so will require more space during the course of committing the
transaction.

There are two levels to this.  One is if the storage medium is full.
In that case, you may not be able to make any progress without
external intervention.  The other case is if the quota assigned to the
database has been exhausted.  There, it really depends on how your
browser handles quota.  If it is a hard quota, you're probably still
DOA.  But if it's a soft quota, just counting the committed space,
then doing a drop or delete may help.

[None of this even starts to address whether DROP or DELETE will
release any space at all.]

-scott


On 10/14/07, Timothy Hatcher <timothy at apple.com> wrote:
>
> You can DROP tables or DELETE all the rows from every table with SQL
> queries. That is what Kristof was inferring.
>
> On Oct 14, 2007, at 7:16 AM, 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.
>
>
> ? Timothy Hatcher
>
>
Received on Sunday, 14 October 2007 15:57:50 UTC

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