Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#22265 closed Cleanup/optimization (fixed)

Assurance of consistent behavior of migrations

Reported by: aruseni Owned by: mardini
Component: Documentation Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

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).

Change History (5)

comment:1 by Sasha Romijn, 10 years ago

Triage Stage: UnreviewedAccepted

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.

comment:2 by mardini, 10 years ago

Owner: changed from nobody to mardini
Status: newassigned

comment:4 by Tim Graham <timograham@…>, 10 years ago

Resolution: fixed
Status: assignedclosed

In bff77e2aa81f90b5be2fd00220b479077d8082de:

Fixed #22265 -- Clarfied consistent behavior of migrations.

Thanks aruseni for the report.

comment:5 by Tim Graham <timograham@…>, 10 years ago

In f847aeb6f88b2a39d32a916b0649330764dc145e:

[1.7.x] Fixed #22265 -- Clarfied consistent behavior of migrations.

Thanks aruseni for the report.

Backport of bff77e2aa8 from master

Note: See TracTickets for help on using tickets.
Back to Top