[whatwg] Comments on updated SQL API

Aaron Boodman aa at google.com
Wed Oct 17 02:29:33 PDT 2007

On 10/17/07, Maciej Stachowiak <mjs at apple.com> wrote:
> - An author mistake (like doing something that causes an exception in
> the callback) means a stuck lock, quite possibly ruining the whole
> session.

I can say from experience that this is a very real problem. It is
probably the number one problem that people run into with the current
Gears API.

Another problem is that developers actually don't realize they need to
use BEGIN and COMMIT and they end up writing extremely slow code and
wondering why. Making the transactions be automatic is a big win for
making the API performant by default.

I think it's worthwhile to iron out the problems with the implicit
transaction and changeVersion, instead of just using a simple api.

- a

More information about the whatwg mailing list