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 07:16:59 -0700
Message-ID: <696e4b7c0710140716m1b752534je6d672c668fdbeda@mail.gmail.com>
OK, that's valid, my devil's advocacy is withdrawn.

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.

-scott

On 10/14/07, Kristof Zelechovski <giecrilj at stegny.2a.pl> wrote:
> As long as the database is readable, I can query all data out of it and
> upload them to a backup server via HTTP.  While this need not be the most
> efficient and secure way to go, there are no software obstacles against.
> Better methods may be invented.
> Best regards,
> Chris
>
> -----Original Message-----
> From: Scott Hess [mailto:shess at google.com]
> Sent: Sunday, October 14, 2007 3:47 PM
> To: Kristof Zelechovski
> Cc: WHATWG Mailing List
> Subject: Re: [whatwg] database full error (was: Re: executeSql API
> issynchronous)
>
> On 10/14/07, Kristof Zelechovski <giecrilj at stegny.2a.pl> wrote:
> > It is possible to recover from a database full error.  You can dump the
> data
> > to a slower device for example.  While this action would not make the
> > database operable again, you would at least avoid losing data.
>
> This is true in the general case, but will you be able to accomplish
> this using JavaScript APIs which are part of the Database spec?
>
> -scott
>
>
Received on Sunday, 14 October 2007 07:16:59 UTC

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