I know that SQLite normally treats multithreading as evil. In Python we have SQLAlchemy and Cherrypy, both are quite sophisticated and handy, but Cherrypy is multithreaded. I have learned that there are ways to force binding a new session
object of SQLAlchemy for each new thread started by Cherrypy, but the thing is, how can I be assured that my data's integrity hasn't been compromised due to this multi-threading issue. What is typical signs of threading-induced data problem? Do they go silently? or you simply cannot commit anything with Sessions
in another thread?
I found this piece of knowledge very critical and yet is a gap in current documentations from both libraries.
Aucun commentaire:
Enregistrer un commentaire