#27631: Prevent execution of transactionnal DDL statements when unsupported.
------------------------------------------+--------------------------------
Reporter: Simon Charette | Owner: Simon Charette
Type: Bug | Status: assigned
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------+--------------------------------
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/27631>
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/052.43e6972c880777f95755c3a1f62521c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
