Add a MoveToMigrations evolution for all built-in Django apps.
Review Request #11075 — Created July 7, 2020 and submitted
We had several Django apps that were still being treated as owned by
Django Evolution, which meant that Django consistently warned about
unapplied migrations. While mostly harmless, this could become a problem
later.This was caused by the lack of a
MoveToMigrations
built-in evolution
for each of these. We set it for a few apps, just the ones that we
needed to apply our own evolutions to at first, but didn't set it for
the remaining ones.This change adds an evolution for this for every built-in Django app
that contains a0001_initial.py
migration.
Evolved the database successfully. Saw the migrations all apply.
Verified that Django no longer complained about missing migrations.
Summary | ID |
---|---|
cb875f2f96811c530730747f09048e9842f549b7 |
Description | From | Last Updated |
---|---|---|
I know these are super tiny, but can we add file docstrings to the top? Same for all 4. |
david |
- Change Summary:
-
- Added file-level docstrings for the new evolution files.
- Added missing changes to unit tests to stop using
django.contrib.admin
for tests involving mutation vs. evolution introspection (since it's now configured for migrations).
- Commits:
-
Summary ID fe8de245f118418fe74a709f01beffba89967c7b cb875f2f96811c530730747f09048e9842f549b7 - Diff:
-
Revision 2 (+116 -24)