> do I need to do a lot of locking? You don't need to do it, SQLite will do that for you. And it doesn't matter whether both applications write to the same table or different ones - as long as they write to the same file those writes will be serialized by locking made inside SQLite.
But you have to be aware of SQLITE_BUSY code that can be returned from SQLite functions, so be sure that you process it properly. Pavel On Tue, Jun 22, 2010 at 12:44 PM, Ian Hardingham <i...@omroth.com> wrote: > Hey guys, > > If I have program 1 and program 2 which both open the same db file, but > they never write to the same table (but might be reading one written by > another), do I need to do a lot of locking? I'm not worried about race > conditions. > > Thanks, > Ian > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
