#5632: Problems with DB objects on a multithreaded scenario
-------------------------------------------------------------+--------------
Reporter: [EMAIL PROTECTED] (alias PyMan) | Owner: nobody
Status: new | Component:
Database wrapper
Version: SVN | Keywords:
multi thread db
Stage: Unreviewed | Has_patch: 0
-------------------------------------------------------------+--------------
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.
--
Ticket URL: <http://code.djangoproject.com/ticket/5632>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
