Yes, it really requires only a little additional work on application side. The native open will open it in read/write share allow, and handle interlocking.
if you get a result of SQLITE_BUSY you need to retry the operation after a short time. On Sat, May 2, 2015 at 4:52 PM, Scott Doctor <scott at scottdoctor.com> wrote: > > I am somewhat new to sqlite and am trying to decide an issue with the > program I am writing (cross platform, written in C/C++). After reading > through the sqlite documentation, I am still unsure about the issue how to > implement multiple instances of the same program. > > Consider a program that may have more than one instance of the same > program open at the same time. Both instances need to read/write the same > sqlite database file. > > Can both instances open the same database file at the same time? > Another way to word the question is whether sqlite will properly handle > two independent programs accessing the same sqlite database file at the > same time where both programs will be reading/writing to the database? Or > do I need to implement or more complex strategy for accessing the sqlite > file? > > -- > > --------------------- > Scott Doctor > scott at scottdoctor.com > --------------------- > > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
