Can I read the database when sqlite throws disk io or image malformed or other critical errors first time. I cannot simulate these issues on my machine. So, I need your suggestion.
On Sun, Dec 9, 2012 at 4:40 PM, dd <durga.d...@gmail.com> wrote: > Thank you Simon Slavin. > > > On Sun, Dec 9, 2012 at 4:27 PM, Simon Slavin <slav...@bigfraud.org> wrote: > >> >> On 9 Dec 2012, at 12:10pm, dd <durga.d...@gmail.com> wrote: >> >> > I have code in C++. Right now, I got this issue on Mac. >> >> Oh. Then you don't have to worry about Windows codepages. All your text >> is already in Unicode. >> >> >>> you still have faulty hardware or software >> > >> > faulty software means? (OS or sqlite version) >> >> The software you wrote. Your C++ code. You may be writing to memory >> that SQLite is using. You may not be allocating or disposing of memory >> correctly. The C programming language is very bad at allowing you to do >> all sorts of dangerous things. Every C programmer makes mistakes like this >> from time to time. >> >> Make sure that you are checking the return values of all your calls to >> the SQLite API, reporting any unexpected values and immediately halting >> your application. That is the easiest way to detect problems as soon as >> they happen. If you don't do this then your application may continue to >> use the database, writing corrupted memory to the database file. >> >> 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
