#24921: No Database objects can be created with set_autocommit(False)
-------------------------------+--------------------------------------
Reporter: shabda | Owner: shabda
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by aaugustin):
* status: assigned => closed
* resolution: => invalid
Comment:
The ORM assumes that Django has control of the database connection,
including control of its transactional behavior.
The docs make it pretty clear that you're on your own in that case:
> Once you turn autocommit off, you get the default behavior of your
database adapter, and Django won't help you.
Other than doing complicated things in `cursor.execute()` calls, I don't
see a use case for disabling autocommit.
Can you clarify what you're trying to do?
--
Ticket URL: <https://code.djangoproject.com/ticket/24921#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.c08af44b0016bda7d4c7a3e60d986dc3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
