Many Thanks for quick reply. Could you please suggest me other journal mode for second case.My target filesytem dosen't support mmap & WAL required mmap support.
Thanks On Wed, Apr 23, 2014 at 3:05 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 23 Apr 2014, at 10:29am, techi eth <techi...@gmail.com> wrote: > > > 1) Sqlite3 doesn’t have any concurrency issue when multiple process > > reading one database file at same time. This doesn’t required any special > > mode setting (Like WAL) > > Correct. > > > 2) One process is reading & other process tries to write the same > > database file then file should be open in WAL mode. > > WAL mode is fine for this. So are other journal modes. But if you like > WAL mode then yes, there will be no problems with it. > > > 3) Sqlite3 doesn’t support Multiple process writing on same time. > > Each connection to the database should set a timeout using one of > > <http://www.sqlite.org/c3ref/busy_timeout.html> > <http://www.sqlite.org/pragma.html#pragma_busy_timeout> > > Set a value of a few seconds. If you do this then if the second process > finds that the database is busy it will wait a while then try again, and > keep waiting until the database is no longer busy. > > If you do not set a timeout then the second process will just return an > error message. > > Simon. > _______________________________________________ > 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
