#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
-------------------------------+--------------------------------------
Comment (by shabda):
To clarify: If this an expected behaviour, then this warning "Once you
turn autocommit off, you get the default behavior of your database
adapter, and Django won't help you." is not strong enough and it should be
calrified that usual ORM methods will fail.
As the docs stand now, it seems to imply that , you get the default
transaction behavior, but can use the ORM. I think a doc or code fix is
needed, so I am going to reopen the ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/24921#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 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.4942f96ec0fd74353c66f5903e1da0cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
