Hi Simon, Thank you for your quick reply.
I am sorry for more general questions. As I mentioned I was getting corrupted db error with sqlite-3.5.9, but when I tried with sqlite-3.6.4 it is no more corrupting the db. -- so was it a bug with sqlite-3.5.9 ? and got fixed in sqlite-3.6.4 -- is it safe to upgrade from sqlite-3.5.9 to sqlite-3.6.14.2 ? as I am working on critical application how safe it is ? Thank you. -Hiral On Thu, Jun 18, 2009 at 4:17 PM, Simon Davies < simon.james.dav...@googlemail.com> wrote: > 2009/6/17 hiral <hiralsmaill...@gmail.com>: > > Hi Simon, > > > > I looked into it but couldn't find the exact reason for my bug. > > > > If you have any idea please let me know. > > Sorry, other than the link, I can not help. > > > > > Also I would appreciate, if you can let me know what does this error > mean > > in terms of btree/pager module of sqlite.... > > > >>> sqlite> PRAGMA integrity_check; > >>> *** in database main *** > >>> Page 5275 is never used > >>> wrong # of entries in index sqlite_autoindex_<table_name>_1 > > Other than that the db is corrupt, I could not say. > If I ever get a corrupted db (from users with unsafe environments), I > extract whatever data it is possible to extract ( see .dump in sqlite3 > command line utility), and reconstruct a new db using that data. > It has not seemed worthwhile trying to analyse/repair a corrupt db. > Identifying where the db has been corrupted will not necessarily > indicate the event that caused it. > > > Thank you. > > -Hiral > > Rgds, > Simon > _______________________________________________ > 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
