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

[whatwg] executeSql API is synchronous

From: Timothy Hatcher <timothy@apple.com>
Date: Thu, 20 Sep 2007 13:14:08 -0700
Message-ID: <45A2B669-9CA8-4B05-BD04-AC3580A2587A@apple.com>
The pain of asynchronous access can be alleviated or even solved with  
an API for transactions, or a group of SQL queries that need be  
executed in order. Commonly, if a transaction fails in the middle, the  
database is rolled-back to the state before the transaction started.

There can then be a callback when the transaction finished or fails,  
with details on what query failed.

On Sep 20, 2007, at 10:13 AM, Aaron Boodman wrote:

> That said, it will be even more common with databases to have  
> multiple asynchronous operations in a row than it is today with XHR.  
> Doing this all asynchronously will be incredibly painful.

? Timothy Hatcher


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20070920/eece8375/attachment.htm>
Received on Thursday, 20 September 2007 13:14:08 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:57 UTC