-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/05/13 22:31, Igor Korot wrote: > Or the simplest one - the database is moved ...
That is sufficient to break the database. A SQLite database is not just the database file, it is also the journal and WAL. If you don't move all as a single unit then you break the database. Often you'll get lucky ... The only safe way to move a database is to use the backup api to make a new copy with the new name. If you do it outside of SQLite then great care has to be taken, and errors won't necessarily be immediately apparent or even show up under pragma check. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGDT0QACgkQmOOfHg372QSkKwCgysgQWSsCWgSN1zMS0p9uOOWb TL8An1MuVaYjysden5anmCnKk2G3+b5w =8HDa -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
