#27631: Prevent execution of transactional DDL statements when unsupported.
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette <charette.s@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"813805833aca60544f6b3d686c015039f6af5d1d" 8138058]:
{{{
#!CommitTicketReference repository=""
revision="813805833aca60544f6b3d686c015039f6af5d1d"
Fixed #27631 -- Prevented execution of transactional DDL statements when
unsupported.
Executing a DDL statement during a transaction on backends that don't
support
it silently commits, leaving atomic() in an incoherent state.
While schema_editor.execute() could technically be used to execute DML
statements such usage should be uncommon as these are usually performed
through
the ORM. In other cases schema_editor.connection.execute() can be used to
circumvent this check.
Thanks Adam and Tim for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27631#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 [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/067.b3086bcdf5be389affc66e29fd01c1f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
