#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 tarkatronic):
An alternative which was suggested, in regards to my specific case, was to
split the data and schema operations into separate transactions, or even
separate migrations. Would something like that be a possibility?
--
Ticket URL: <https://code.djangoproject.com/ticket/25492#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/069.4b973258db9dc6367fcdcd02940ca2e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
