#24921: No Database objects can be created with set_autocommit(False)
-------------------------------------+-------------------------------------
Reporter: shabda | Owner: aaugustin
Type: Bug | Status: assigned
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* has_patch: 0 => 1
Comment:
After further analysis, the check that raises an exception in that case
can simply be removed. See https://github.com/django/django/pull/5330 for
details.
It won't work on SQLite for the usual reason, namely
http://bugs.python.org/issue10740.
My original design for transaction was very stringent. Then I relaxed it,
for instance I introduced `savepoint=False`. This is one more logical step
in this direction.
I'm hesitating to backport this patch to 1.8 LTS. It could be considered a
significant problem in the transaction functionality.
--
Ticket URL: <https://code.djangoproject.com/ticket/24921#comment:16>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.dfc823ec0c12a3c42ebb33cf4789a880%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
