On Apr 22, 2008, at 6:52 PM, Scott Hess shess-at-google.com |sqlite| wrote:
> Weirdo response, but ... make sure you have HAVE_USLEEP defined. We > kept seeing something similar, and kept looking at the code for > sqliteDefaultBusyCallback(), and the code looked right, but the > problem remained, until we eventually started questioning every > assumption. At which point we found that we needed to add > -DHAVE_USLEEP=1 somewhere. > > Also, you should note your platform. > > Anyhow, another solution would naturally be to use a mutex to prevent > multiple writers from getting in. Depending on your app's structure, > this can be pretty annoying to add on top... > > -scott > Sorry, I should have said that this is on Windows XP. I considered using a mutex but since transactions do their own mutexing it seemed redundant to layer my own on top. I also thought I had read somewhere on sqlite.org that SQLite had write-starvation improvements in recent releases, so I wanted to make sure I wasn't missing something obvious. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
