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

[whatwg] Asynchronous database API feedback

From: Brady Eidson <beidson@apple.com>
Date: Wed, 12 Dec 2007 10:33:05 -0800
Message-ID: <671E91C1-928B-4B63-B2F7-17F6798EC227@apple.com>
I think the issue you're forgetting is when opening a transaction can  
fail.  The transaction callback is only called when the transaction is  
successfully opened and you know that it is starting out valid.

~Brady

On Dec 12, 2007, at 9:37 AM, Dimitri Glazkov wrote:

> .. Speaking of batches, in my adventure of implementing the new SQL
> spec, it looked like the transaction callback is mostly a functional
> equivalent of a queue.
>
> So, one idea would be explicitly make it an queue-like structure,
> rather than a function callback:
>
> var db = openDatabase('test');
> var tx = db.createTransaction();
> tx.add(db.sql('create table if not exists chickadees(name text, kind  
> text)'));
> tx.add(db.sql('insert into chickadees values(?, ?)', ['moesha',
> 'black-capped']));
> tx.add(db.sql('select * from chickadees', [], function(rs) {
> console.log(rs.rows.name); }));
> tx.execute(function(error) {
> 	console.log('bird flip!');
> });
>
> .. in which case single statements could be executed as:
>
> db.sql('select count(*) as count from chickadees', [], function(rs) {
> console.log(rs.rows.count); }).execute();
>
> What do you think?
>
> :DG<
Received on Wednesday, 12 December 2007 10:33:05 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:38 UTC