11396 2010-11-24 06:21:29 +0000 Add a callback to IDBDatabaseSync.transaction 2011-03-08 03:42:43 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified All All RESOLVED FIXED P2 normal --- 1 pablo.castro dave.null jorlow mike public-webapps public-webapps-bugzilla oldest_to_newest 42745 0 pablo.castro 2010-11-24 06:21:29 +0000 In the TPAC folks proposed to tweak the sync API such that it prevents code patterns that cause deadlocks at the start of a transaction. We ended up with a proposal where we'd add a callback to IDBDatabaseSync.transaction, and work in that transaction can only happen within the callback. The change would be: - add a callback argument to IDBDatabaseSync.transaction(), the callback will receive one argument that's the transaction object - once the callback returns, the transaction is committed - if an exception is thrown and not caught inside the callback then the transaction must be aborted - make the method void, no transaction object is returned - a call to transaction() from within a transaction callback or an async API callback that involves a transaction will fail with NOT_ALLOWED_ERR. 42747 1 jorlow 2010-11-24 10:48:38 +0000 It's worth making clear that the callback will be called synchronously. (i.e. no code after the transaction call will execute until after the callback executes (if it'll ever execute). The callback is just to make the scope of the transaction more explicit.