Thank you for your feedback Aymeric,
I have added the backward migration method + tests per your suggestion:
https://github.com/django/django/pull/10381/commits/d5c4a4b08ccee9239e5117df4c788a5a7a2f60a9
Regards
—
Arthur
On January 6, 2019 at 10:04:18 PM, Aymeric Augustin (
aymeric.augus...@poly
Hello Arthur,
I agree that option 1 is the way to go.
It would be nice to make the migration reversible. If someone upgrades to
Django 2.2.x, migrates the database, and later discovers a blocking issue, they
should have the option to migrate backwards and downgrade to 2.1.y.
Best regards,
--
Hi all,
I have been working on a 9 years old ticket that I'd like to close once and
for all. The outstanding question is about the migration path to choose in
order to update existing proxy model permissions. I have explained three
different approaches I can think of in the pull
request: https
