Adam Johnson - Fri, 15 May 2020 at 17:53:21 > At least two of the major database servers that Django supports, PostgreSQL > and MySQL, provide zero downgrade-ability. It's too hard for them to do.
while this is now officially true for both MariaDB and MySQL, until recentlyish it was possible to downgrade them after carefully reading changelogs. This is now unsupported and even runtime errors are generated. AFAIK postgresql is/was always safe to upgrade/downgrade if staying on the same major version. having said that i think downgradability requires massive engineering resources for very little return in case of a project like django. long story short: never upgrade without reading changelogs, running the testsuites, and deploying on test/staging first. It's not simply a matter of bumping a number in requirements.txt, although it has happened many times that no other changes were required :} -f -- -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20200515231835.GB3895%40obiit.org.
