On 7 October 2010 09:12, vishvananda <email address hidden> wrote:
> Sqlite locks the database and doesn't support dealing with threads that
> well. That said, if you can put up with an occasional error with the
> services failing to update, it seems to run fine. Perhaps we could
> specifically check for locked database in the services update call and
> just print a warning instead of an error.
Why don't we add check_same_thread=False to sqlite.connect ? swift team took
a lot of time to tackle the sqlite locking problem (and others) maybe we can
learn from them ?
On 7 October 2010 09:12, vishvananda <email address hidden> wrote:
> Sqlite locks the database and doesn't support dealing with threads that
> well. That said, if you can put up with an occasional error with the
> services failing to update, it seems to run fine. Perhaps we could
> specifically check for locked database in the services update call and
> just print a warning instead of an error.
Why don't we add check_same_ thread= False to sqlite.connect ? swift team took
a lot of time to tackle the sqlite locking problem (and others) maybe we can
learn from them ?
Chmouel.