This is probably taking us down another path, but how would my query succeed at all if I need a lock to read and the DB file itself is read-only?
My normal queries do work fine, even if the directory is mounted read-only. --Mark -----Original Message----- > Date: Mon, 25 Apr 2016 09:14:14 -0400 > From: Richard Hipp <drh at sqlite.org> > To: SQLite mailing list <sqlite-users at mailinglists.sqlite.org> > Subject: Re: [sqlite] sqlite3 command line, read-only > > On 4/25/16, Mark Foley <mfoley at novatec-inc.com> wrote: > > > > I wonder, then, why I get a lock error if the database is read-only in the > > first > > place? > > The reader has to get a read lock in order to prevent a concurrent > writer from changing content out from under it. (Moving the database > to WAL mode allows readers and writers to co-exist.) > > -- > D. Richard Hipp > drh at sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
