We had a similiar issue with Postgres + Mod_Apache, so I don't think Twisted
& MySQL is related. What we found we had to do:
cursor = connection.cursor()
cursor.execute("UPDATE .... blah blah SQL blah")
transaction.commit_unless_managed()
I never spotted the transaction.commit_unless_managed() in the
documentation, but I found it in the Django code daily_cleanup.py (for
cleaning the session data).
http://code.djangoproject.com/browser/django/trunk/django/bin/daily_cleanup.py
Hope this helps.
-joe
On 1/6/07, Ilia Kantor <[EMAIL PROTECTED]> wrote:
Hello!
I'm using django with Twisted + Mysql.
The problem is that cursor for same SQL returns same results between
requests if connection.commit() was not called.
Sometimes that's a problem, because data is changed by other clients, and
commit never happens.
Autocommit mode is fine and it fixes the problem (hence it has nothing to
do with result caching), but I have to patch django for it.
I can call commit before every select, but it's just ugly..
Is there a solid way to go ?
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
