3 ms·
Should be noticed, the semantics of SQLite behavior in multithreaded mode is pretty cryptic, even to its long-term users (and others just silently give up, and
by mlvljr 12y ago
Should be noticed, the semantics of SQLite behavior in multithreaded mode is pretty cryptic, even to its long-term users (and others just silently give up, and hand-roll coarse-grained locks, I suspect):
http://sqlite.1065341.n5.nabble.com/think-I-need-better-error-handling-guidance-in-the-C-API-td76332.html http://sqlite.1065341.n5.nabble.com/think-I-need-better-erro...
- couchand 12y agoThe linked discussion has one of the most succinct comments about error handling I've seen. You handle the result codes you know what to do with, and everything that remains means your program should explode immediately.
- mlvljr 12y ago:) problem is, there's no clear understanding of how one can avoid the possibility of unwanted error codes ever returned in his program, but yes