We have an application that we distribute to our clients each of whom run Windows - often it's a desktop XP machine. Our app consists of a set of Delphi services and a PHP web front end each of which use ODBC for database connectivity.
The vast majority of installations have shipped with sqliteodbc-0.83 (sqlite 3.6.14.2). Over several weeks a number of these installations have broken down - our support staff have noticed problems with the sqlite databases which turn out to be corrupt. We recently began shipping a third component - a Java app which again connected by ODBC. However, it used threads and the database fell over inside of hours. We found and fixed mulitple thread safety issues and the rate of corruption reduced signficantly. However the corruption issue remained albeit smaller in frequency. In the past month or so we have tested more intensively with sqliteodbc-0.88 (sqlite 3.7.4 and 3.7.5 with our own build). We can still corrupt the database however. So a couple of weeks ago we switched to using WAL mode which so far hasn't had any corruption to my knowledge. I suspect that we are avoiding the root cause by switching the behaviour of sqlite on disk. My question is does anyone have pointers to help us isolate the problems we are seeing. We can obviously provide further detail to your questions. Many thanks, James _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
