Main question/comment: ----- On the "how to corrupt" page ( http://sqlite.org/howtocorrupt.html ) i do not see any mention of using SQLite in an incorrect way with respect to thread safety. Is there really no way that, for example, using the same connection on multiple threads at the same time could either (a) corrupt the database, or (b) lead to a false reports of corruption?
(Even if such a misuse of SQLite falls under one of the categories already listed on the page, perhaps said category could be updated to explicitly tell about the risk of misusing SQLite in this way... perhaps a "Section 2.6"... or 5.1 or 7.1). Thoughts? -P P.S./Appendix: Further background info (probably TMI)... ----- We are trying to help a client debug some issues in a Xamarin-based app that is deployed to both Android and iOS. Some of the errors they are seeing are "malformed database". They are still building in a way that uses the platform-provided SQLite on both platforms (no, this will not work on Android N) and no additional SQLite library is linked in, so they should not be having the "Multiple copies of SQLite linked into the same application" problem. They also routinely see "cannot start a transaction within a transaction" even though there is no obvious place where or reason why that would happen in their code. This leads us to believe they may be using the same connection on multiple threads. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
