W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: [IndexedDB] IDBCursor.update for cursors returned from IDBIndex.openCursor

From: Shawn Wilsher <sdwilsh@mozilla.com>
Date: Wed, 22 Sep 2010 09:48:29 -0700
Message-ID: <4C9A335D.1030409@mozilla.com>
To: Jonas Sicking <jonas@sicking.cc>
CC: Jeremy Orlow <jorlow@chromium.org>, public-webapps WG <public-webapps@w3.org>
On 9/17/2010 3:14 PM, Jonas Sicking wrote:
> How do you then guarantee that a transaction that spans multiple
> objectStores either fully succeeds or is fully rolled back? Especially
> in the event of a crash during commit.
If you don't use write ahead logging, and connect to each database with 
ATTACH, SQLite makes sure it is atomic for you (I don't recall how 
offhand though).  Not using write ahead logging does mean that writers 
will block readers though.



Received on Wednesday, 22 September 2010 16:50:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:11 UTC