Hi Richard, Thanks for the quick reply.
So what I am confused is, if there is a Write (update) operation and it creates a WAL file and subsequently a read operation comes in and the read is trying to access the same data what write is working on. Does in this scenario read will wait or it will grab the data from the original database file which is not really data? Harnek -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard Hipp Sent: April-30-12 4:30 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Concurrency On Mon, Apr 30, 2012 at 7:17 PM, Harnek Manj <[email protected]>wrote: > Hi, > > I am trying to make sqlite available for concurrency within a process > and multi-process. > WAL mode. 5. Read about WAL, it gives the concurrency. But I think it gives > concurrency by allowing dirty reads. Please correct me if I am wrong. > Isolation in WAL mode is SERIALIZABLE. Please help me to improve the documentation for SQLite by telling me what you read in the documentation that lead you to believe that WAL mode gaves dirty reads? -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
