#31632: Single queries without transaction do not follow AUTOCOMMIT
-------------------------------------+-------------------------------------
Reporter: Filipe Pina | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Filipe Pina):
I don't usually run with MySQL (PG favorite choice), so I don't know how
often these sort of bugs come up or how you tackle them.
But as a developer that uses Django, I wouldn't mind if instead of
"working around" external bugs, a warning would be raised (with unique
name to be suppressed, if desired), something along the lines:
```
mysqlclient <=1.4.6 (TBC) always reports server autocommit as True so
Django is unable to choose whether to change it or not.
To avoid unexpected issues, set it to 1 globally in your MySQL instance or
add `set autocommit = 1` to your `init_command`.
```
--
Ticket URL: <https://code.djangoproject.com/ticket/31632#comment:14>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.988f809c05531baeb23c4baade4ecd57%40djangoproject.com.
