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

[whatwg] SQL API error handling

From: Křištof Želechovski <giecrilj@stegny.2a.pl>
Date: Thu, 18 Oct 2007 23:16:46 +0200
Message-ID: <000901c811cc$358a3630$4d01010a@IBM42F76C011DF>
It is normal that the disk gets full; the probability of this event is 1 for
a consumer disk.  (Admittedly, the operating system can cry aloud and refuse
to do anything when the startup volume is about to overflow but the database
could be stored on another volume that is not protected that way).  OTOH, it
is an exceptional situation that data become corrupt.  Therefore these two
situations are not equivalent.
Best regards

-----Original Message-----
From: whatwg-bounces@lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Brady Eidson
Sent: Thursday, October 18, 2007 4:51 AM
To: Ian Hickson
Subject: Re: [whatwg] SQL API error handling

Corruption in the database isn't the fault of the user agent.  I  
consider it at the same level as corruption on disk - or even a full  
As I consider these to be similar, I assert that database corruption  
is an external force the user agent - and potentially the application  
it hosts - needs to be ready to handle.
Received on Thursday, 18 October 2007 14:16:46 UTC

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