On 22 Jun 2010, at 5:44pm, Ian Hardingham wrote: > 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.
SQLite will need to do locking for you, because SQLite locks the entire database rather than just one table or one row. You must monitor the codes returned from your calls, dealing with SQLITE_BUSY and SQLITE_LOCKED accordingly. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
