#22265: Assurance of consistent behavior of migrations
--------------------------------------+--------------------
Reporter: aruseni | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+--------------------
> Migrations will run the same way every time and produce consistent
results, meaning that what you see in development and staging is exactly
what will happen in production - no unexpected surprises.
I think it is a ''technically'' correct assertion, but actually the user
may have a completely different data on the production machine. Which
means the migrations ''will'' work the same way, but it won’t necessarily
lead to the same result (which is actually the thing some users will
expect after they have read such assurance of consistent behavior). For
instance, some errors will only occur with specific data (which may be
only on the production server).
--
Ticket URL: <https://code.djangoproject.com/ticket/22265>
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/050.adc0b983ca42dc5e67b8d185b75d2515%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
