#3279: threading fastcgi does not work with mysql, raising 'ReferenceError:
weakly-referenced object no longer exists'
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: closed | Component: Core framework
Version: SVN | Resolution: worksforme
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------+---------------------------------------
Changes (by [EMAIL PROTECTED]):
* component: Admin interface => Core framework
* summary: MySQL connections.py ReferenceError: weakly-referenced object
no longer exists => threading fastcgi does not
work with mysql, raising 'ReferenceError:
weakly-referenced object no longer exists'
Comment:
If django with threading-flup uses one global connection object and
multiple cursors created from the global connection object, this is not
going to work, see:
http://forums.mysql.com/read.php?50,104391,104688#msg-104688
Regarding threading and PostgreSQL, there's a lot to say why you shouldn't
do threading with python on Linux, but please ask on the user list. I'd
like to keep the ticket clean and separate from user support, as a long
ticket with sidelines will be difficult to read.
Before I put this ticket forward, I'm going to find out about whether
there's a global connection object or whether I can verify this, but this
might take until Monday or Tuesday.
--
Ticket URL: <http://code.djangoproject.com/ticket/3279#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
