By default sqlite3 is fairly safe, so when you change a pragma ensure that you are not disabling a safety feature.
To get an idea, check this thread where I had the opposite need (more speed, less safety) http://sqlite.1065341.n5.nabble.com/What-pragma-to-use-to-get-maximum-speed-at-expense-of-safety-td68488.html About backups, here is the documentation: http://www.sqlite.org/backup.html I personally always used the historical way. And copied the backups in a remote server. On Fri, Jul 19, 2013 at 12:00 PM, techi eth <techi...@gmail.com> wrote: > Thanks for answer. > > I can do integrity check by PRAGMA integrity_check.Please correct me if i > wrong. > Here backup means copying database file OR we can create query to SQLite > for backup or copy. > > Cheers- > Techi > > > > On Wed, Jul 17, 2013 at 4:42 PM, Paolo Bolzoni < > paolo.bolzoni.br...@gmail.com> wrote: > >> On Wed, Jul 17, 2013 at 12:55 PM, techi eth <techi...@gmail.com> wrote: >> > 2) How do we make database safe from these error Or What is >> Possibility to >> > access database after error. >> After error, as Stephan said you are out of luck. >> >> You should avoid this errors in the first place: >> - make backup often, >> - keep the safety features of sqlite3 on, >> - use a error resilient filesystem (e.g., zfs), >> - use ecc memory. >> _______________________________________________ >> 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 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
