Hi Richard, Sorry, i gave a wrong version number of sqlite . We are using sqlite 2.8.13.
OBSERVATIONS: ------------- 1) If i call sync() system call after database update, the database is not getting corrupted. 2) In one scenario of corruption sqlite_open() returned an error message "file is encrypted or is not a database". 3) In another scenario sqlite_open() did not detect the corruption. But any subsequent calls is not successful. For example if we start sqlite application and run .tables , nothing is returned. Thanks and regards Jayanth On Fri, 06 Oct 2006 [EMAIL PROTECTED] wrote : >"jayanth KP" <[EMAIL PROTECTED]> wrote: > > Hi, > > I have a question regarding power failure handling in sqlite 2.8.3. > > > > When the power is switched off during a database write like > > (insert/update), in next reboot database is getting corroupted. > > > > The database is in a ext3 partition on the harddisk (linux 2.6). > > > > > > Also i tried the following in my c code after sqlite_open() was success. > > > > sqlite_exec(pDbHandle,"PRAGMA synchronous=FULL;", NULL, NULL, &pErrMsg); > > > > This did not seem to work. > > > > Please help me in solving this issue > > > >See http://www.sqlite.org/cvstrac/tktview?tn=599 > >This problem was fixed in SQLite version 2.8.12, over two >and a half years ago. > >-- >D. Richard Hipp <[EMAIL PROTECTED]> > > >----------------------------------------------------------------------------- >To unsubscribe, send email to [EMAIL PROTECTED] >----------------------------------------------------------------------------- >
