The behavior seems to have reverted after a couple days. I suspect
that the connection to mysql is being renegotiated, during which it
loses the autocommit setting.
This seems like it should be a setting in django, so if it
renegotiates it will set autocommit again.
Another solution might be to e
Thank you!
'set transaction isolation level read committed' had no effect, but
'set autocommit=1' appears to fix it.
I wondered if there was some more general way of doing this (I mean,
besides passing in raw sql). Perhaps the set_autocommit() method in
db.backends.creation?
On Fri, Jan 28, 20
On Fri, Jan 28, 2011 at 9:45 PM, Brian Craft wrote:
> Digging into the problem I'm having with a standalone django script,
> the problem seems to be that django doesn't see updates to the
> database unless it writes to the database.
>
Sounds a lot like:
http://groups.google.com/group/django-users
3 matches
Mail list logo
