10 messages in com.googlegroups.google-gearsRe: Global variable and DB locks in w...
FromSent OnAttachments
Sam03 Oct 2007 13:02 
Scott Hess03 Oct 2007 13:17 
Scott Hess03 Oct 2007 13:19 
Aaron Boodman03 Oct 2007 13:35 
Sam04 Oct 2007 00:06 
Sam04 Oct 2007 00:21 
Aaron Boodman04 Oct 2007 01:00 
Sam04 Oct 2007 02:55 
Sam04 Oct 2007 03:00 
Scott Hess04 Oct 2007 09:32 
Subject:Re: Global variable and DB locks in worker pool,
From:Sam (savi@yahoo.co.in)
Date:10/04/2007 12:21:14 AM
List:com.googlegroups.google-gears

On Oct 4, 1:35 am, "Aaron Boodman" <a.@google.com> wrote:

If one tries to write while another one already is, the second one's call to execute() will be slower (because it is waiting for the first to be done), but it will work.

So you mean if a worker encounters an SQLite busy signal on any DB operations, it will automatically wait until the DB is free to resume the operation (i.e. the developer doesn't have to code to check for the busy signal and initiate a wait timer etc. etc.)?