#22496: Data migrations are not transactional (except on Postgres)
-------------------------------------+-------------------------------------
Reporter: shai | Owner: nobody
Type: Bug | Status: new
Component: | Version: master
Migrations | Keywords: oracle mysql sqlite
Severity: Release | Has patch: 0
blocker | Needs tests: 1
Triage Stage: Accepted | Easy pickings: 0
Needs documentation: 1 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
In e74d2183c28467aefc0b87e3fa6d405dbfdea82c (master) and
9bf890f6f9d137d5b86fd9a6a38fb11c5d21b1af (1.7.x) schema editor was made
not to open transactions for backends that cannot roll back DDL. However,
there is nothing else that starts transactions in migrations, even if they
are data migrations -- so now, of the backends in core, migrations are
only transactional on PostgreSQL.
This is a spin-off from #22483.
--
Ticket URL: <https://code.djangoproject.com/ticket/22496>
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/047.ddbcb33ef075c0c1b95d115eda212505%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
