[Django] #22265: Assurance of consistent behavior of migrations
Django
--------------------------------------+--------------------
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.
Django
Reporter: aruseni | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
Changes (by erikr):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
I think this is a valid point - the current text is very strong in its
assertion, and this may hit some users unexpectedly. I agree we should add
a sentence to mention the case you describe.
--
Ticket URL: <https://code.djangoproject.com/ticket/22265#comment:1>
Django
Reporter: aruseni | Owner: mardini
Type: Cleanup/optimization | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Easy pickings: 1 | UI/UX: 0
Changes (by mardini):
* owner: nobody => mardini
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/22265#comment:2>
Django
Reporter: aruseni | Owner: mardini
Type: Cleanup/optimization | Status: assigned
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Easy pickings: 1 | UI/UX: 0
Comment (by mardini):
Pull Request: https://github.com/django/django/pull/2470
--
Ticket URL: <https://code.djangoproject.com/ticket/22265#comment:3>
Django
Reporter: aruseni | Owner: mardini
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Easy pickings: 1 | UI/UX: 0
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"bff77e2aa81f90b5be2fd00220b479077d8082de"]:
{{{
#!CommitTicketReference repository=""
revision="bff77e2aa81f90b5be2fd00220b479077d8082de"
Fixed #22265 -- Clarfied consistent behavior of migrations.
Thanks aruseni for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22265#comment:4>
Django
Reporter: aruseni | Owner: mardini
Type: Cleanup/optimization | Status: closed
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Easy pickings: 1 | UI/UX: 0
Comment (by Tim Graham <timograham@…>):
In [changeset:"f847aeb6f88b2a39d32a916b0649330764dc145e"]:
{{{
#!CommitTicketReference repository=""
revision="f847aeb6f88b2a39d32a916b0649330764dc145e"
[1.7.x] Fixed #22265 -- Clarfied consistent behavior of migrations.
Thanks aruseni for the report.
Backport of bff77e2aa8 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22265#comment:5>