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

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

From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
Date: Sun, 14 Oct 2007 15:55:35 +0200
Message-ID: <001901c80e69$e5583fa0$1a01080a@POCZTOWIEC>
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,

-----Original Message-----
From: Scott Hess [mailto:shess@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

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
> 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?

Received on Sunday, 14 October 2007 06:55:35 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:58 UTC