zulip

Author	SHA1	Message	Date
Anders Kaseorg	de1fb2b8d0	check-database-compatibility: Ignore guardian, django.contrib.sites. We can safely ignore the presence of the extra tables that could be left behind in the database from when we had these installed (before Zulip 1.7.0 and 2.0.0, respectively). Signed-off-by: Anders Kaseorg <anders@zulip.com>	2022-03-01 10:30:23 -08:00
Tim Abbott	98a05257ea	scripts: Print names of missing migrations in compatibility check. This will make it much easier to debug any situations where this happens.	2022-02-28 11:09:52 -08:00
Tim Abbott	1a7c4a0276	scripts: Fix typo in logging statement.	2022-02-11 13:47:24 -08:00
Alex Vandiver	8da6098631	upgrade: Catch "upgrade" attempts which would downgrade the database. Attempting to "upgrade" from `main` to 4.x should abort; Django does not prevent running old code against the new database (though it likely errors at runtime), and `./manage.py migrate` from the old version during the "upgrade" does not downgrade the database, since the migrations are entirely missing in that directory, so don't get reversed. Compare the list of applied migrations to the list of on-disk migrations, and abort if there are applied migrations which are not found on disk. Fixes: #19284.	2022-02-10 16:02:49 -08:00