On Thu, Sep 6, 2012 at 5:26 PM, Simon Slavin <slav...@bigfraud.org> wrote:
> > On 6 Sep 2012, at 3:13pm, Richard Hipp <d...@sqlite.org> wrote: > > > If the last writer to the database file crashed and left a hot > > journal<http://www.sqlite.org/atomiccommit.html#section_4_2>then the > > next reader to come along must rollback that journal before it can > > start reading, and that will require write access. We have encountered > > cases where companies accidently publish a gazillion copies of a CDROM > that > > contains a hot journal. The database on such CDROMs are unreadable. > > Ouch. Yeah, I guess that's going to happen occasionally. > Not that I think this is necessarily a good idea, but maybe if opening a database with a hot journal from read-only media (or with _READONLY), the database pages in the journal can be loaded into the page cache and marked as never_remove_from_cache or some such, effectively giving read-only access to the database (I think this would work, but might not be a good idea. But that company would have saved their reputation if this existed) -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
