#25492: warn about migrations mixing schema- and data- changing operations
--------------------------------------+------------------------------------
Reporter: tarkatronic | Owner: nobody
Type: New feature | Status: new
Component: Core (System checks) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by timgraham):
Each migration is run in a separate transaction, so yes, splitting the
operations into separate files is what you should do. We don't want to run
multiple transactions per migration because we need each migration to be
atomic.
--
Ticket URL: <https://code.djangoproject.com/ticket/25492#comment:5>
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/069.2f6f0b05831e1bf1884697d3581a6b31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
