W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2013

Re: [IndexedDB] Inform script of corruption recovery

From: Kyaw Tun <kyawtun@yathit.com>
Date: Mon, 20 May 2013 11:14:12 +0800
Message-ID: <CAFPCW95xBmfUFD=KZHDEa-TCujACDPX=rjnzUiTa8N74Pwxu7Q@mail.gmail.com>
To: Webapps WG <public-webapps@w3.org>
It will be good, if we can provide data priority per database and/or per
object store.

Web app already assume Indexeddb data is temporary, recovery process are in
place at the beginning after database is successfully open. So silently
drop all data and set version to 0 is good way to go. I think detail reason
are not necessary.

After opening, database should not corrupt. But quota exceed error do
happen. It is very difficult and messy to handle that issue.

If these corruption happen, data are lost according to their priority will
be good enough for most situation. It is easy for both sides (developer and
browser implementation).

Received on Monday, 20 May 2013 03:14:43 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:55 UTC