On Wed, May 12, 2010 at 06:23:46AM -0500, Black, Michael (IS) scratched on the wall: > Somebody please correct me if I'm wrong on this one... > I think sqlite can work with multiple processes just doing read-onliy > operations (like SELECT).
Yes. > It's just the write operations > (INSERT/UPDATE) which will cause SQLITE_BUSY to occur. "Cause", yes, but both readers and writers can get an SQLITE_BUSY return code. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our opponent is an alien starship packed with atomic bombs. We have a protractor." "I'll go home and see if I can scrounge up a ruler and a piece of string." --from Anathem by Neal Stephenson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
