Hello Nithin, Thursday, November 13, 2008, 12:15:57 AM, you wrote:
NJ> Hi, NJ> The problem is that the process is crashing without giving me a NJ> chance to detect the error and recover from the situation. How can I NJ> prevent that? NJ> How can I programatically find out the the corrupted rows? If I can NJ> find these rows I can work around them. NJ> Thanks in advance NJ> Nithin NJ> _______________________________________________ NJ> sqlite-users mailing list NJ> sqlite-users@sqlite.org NJ> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users Well, in windows you can use "Structured exception handling" to catch crashes before they take out your program. In my program, I do an integrity check on many DB's before I use them. I consider a damaged DB to be a fatal error so, I rename and open a new one. Most of the data I store though isn't mission critical. I use SEH try catch blocks around the more dangerous code in my program. -- Best regards, Teg mailto:[EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
