id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux 5632 Problems with DB objects on a multithreaded scenario claudio.marinozzi@… nobody "Discussion topic that started here in [http://groups.google.com/group/django-developers/browse_thread/thread/905f79e350525c95 Django Developers] There are some critical functions like get_or_create, create, delete, add, remove, etc. that if used in a multithreaded scenario could be crash or ""damage data"" (some samples in the discussion above) when working on same DB-data, or even not, at the same time. These operations should be serialized (mutexed) or something like that. I attach a diff file containing the quick, but working, solution. It's a decorated function used on those critical functions that does the mutex thing. Maybe the decoration should be added to some other functions too. Still don't know Django that good. " closed Database layer (models, ORM) dev invalid multi thread db Accepted 1 0 0 0 0 0