#17771: weird problem db with autocommit
-------------------------------------+-------------------------------------
Reporter: meister | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.3
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by meister <admin@…>):
* status: new => closed
* resolution: => wontfix
Comment:
Replying to [comment:3 meister <admin@…>]:
> Replying to [comment:2 akaariai]:
> > The problem seems to be that you are running in a transaction with
repeatable read semantics. I don't think Django supports autocommit for
MySQL.
>
> It doesn't explain why my code works on some environments and do not
work on others...
It works when using MyISAM and creates some problem with InnoDB. My
problem is explained in http://groups.google.com/group/django-
users/msg/55fa3724d2754013?pli=1.
--
Ticket URL: <https://code.djangoproject.com/ticket/17771#comment:4>
Django <https://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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
