On 12 Apr 2011, at 10:15am, James Green wrote: > 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).
Was it built threadsafe ? See http://www.sqlite.org/threadsafe.html > 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. You don't mention which parts of the documentation you're aware of, so I'll point to the above and section 6 of <http://www.sqlite.org/lockingv3.html> just in case. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
