On Thu, 2 Jul 2009 14:21:44 +0200, Jean-François Smigielski <[email protected]> wrote:
>Hello, list! > >I am currently using SQLite Databases (v3.5.8) stored on NAS servers and I >have to take snapshosts of these storage devices. The snapshots must be >accessible, and the database files can be found in well-named directories >whose content has read-only permissions. > >My problem is that hot-journal files are snapshot'd too. When I try to open >a DB file having such a journal, the opening fails. The user has read >permissions (according to the file permissions) on the database file itself, >but that the FS that is read-only. You have to allow the database to be written to, because the snapshot version is inconsistent and can't be queried reliably. It will be recovered using the journal by the first SQLite-capable program that opens it. Snapshots aren't meant to be written in. You'll have to copy the database and its journal from the virtual directory (=snapshot) to a normal directory to allow the recovery to take place. >I tried several PRAGMA to ignore the -journal files but I didn't get >satisfaction. I still have the possibility to patch sqlite3 itself, but I >hope there will remain another possibility. > >Can you please help me? Any URL, advice or code sniplet will be welcome. >Please let me know if you need more information. > >Thanks, -- ( Kees Nuyt ) c[_] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
