No, this is definitely not the reason in my case as I can reproduce this issue on every 3.7.2/3.7.3 machine I've tested after copying the database file (and only the database file) to these machines.
Am 15.11.2010 15:41, schrieb Kirk Clemons: > Not sure if it helps but I would see this quite frequently when an old > journal file would be left behind in the same directory as the backup > database. This could be why making a change to the database such as vacuum > would prevent the corruption. > _______________________________________________ > 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
