22370 2013-06-14 22:34:57 +0000 Inform script of corruption-induced data loss 2015-08-10 20:10:54 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED MOVED P2 normal --- 1 dgrogan dave.null jsbell mike public-webapps public-webapps-bugzilla oldest_to_newest 89336 0 dgrogan 2013-06-14 22:34:57 +0000 It would be nice to be able to notify script that some data may have been lost due to disk corruption or other failure. This was discussed some in [thread], with the leading idea being an attribute on the upgradeneeded and success events that are fired at open requests. The attribute's could be called "dataLoss" with values including "none", "total", or "partial". The chrome implementation has been started, see [chromebug]. [thread] http://lists.w3.org/Archives/Public/public-webapps/2013JanMar/0355.html [chromebug] https://code.google.com/p/chromium/issues/detail?id=172626 89337 1 dgrogan 2013-06-14 22:35:39 +0000 Marking RESOLVED LATER to denote that it should be considered for V2, not V1. 95617 2 dgrogan 2013-10-31 17:29:32 +0000 We have heard from web application developers that they want even more transparency into what is causing data loss. Chrome is going to ship a dataLossMessage alongside dataLoss on the upgradeneeded event, as described in this thread: http://lists.w3.org/Archives/Public/public-webapps/2013OctDec/0108.html 119813 3 jsbell 2015-04-23 15:56:26 +0000 As dgrogan@ noted, we shipped IDBVersionChangeEvent#dataLoss and IDBVersionChangeEvent#dataLossMessage in Chrome, and it's seeing use. Since they're not widely publicized entry points we're open to alternate suggestions. 122542 4 jsbell 2015-08-10 20:10:54 +0000 Moved to https://github.com/w3c/IndexedDB/issues/30