| Age | Commit message (Collapse) | Author |
|
unique_together is removed from a model.
|
|
|
|
|
|
|
|
|
|
Thanks to Chris Beaven.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This inspects the migration operation, and if it is not in the
django.db.migrations module, it adds the relevant imports to the
migration writer and uses the correct class name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Thanks to bendavis78 for the test and diagnostic work.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #22605, #22735; also lays the ground for some other fixes.
|
|
Fixed #22725 - Migration.run_before does nothing
|
|
Thanks to Trac alias tbartelmess for the report and the test project.
|
|
`makemigrations` will automatically create the package specified
in `MIGRATION_MODULES` if it doesn't already exist.
Thanks ovidiuc4 for the report.
|
|
This attribute (used for reverse dependencies) was previously declared
and mentioned in the code, but never actually used.
|
|
Made the fix in InteractiveMigrationQuestioner class code, rather than
MigrationAutodetector, because --dry-run shouldn't affect whether
MigrationAutodetector will detect non-nullable fields, but the
questioner should skip the question and returns a None for default
(since that won't be used anyway) if --dry-run is used.
|
|
Thanks rockallite.wulf for the report.
|
|
Nested deconstruction should (silently) handle Field.deconstruct() as
well as other arbitrary deconstructable objects. This allows having a
field in the deconstruction of another field.
|
|
This reverts commit a4737bf6ae36a5f1cb29f2232f6deeff084fabff.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You're not allowed to do this after you've made migrations; see ticket
for more details.
|
|
|
|
In some cases, this could lead to migrations written with Python 2
being incompatible with Python 3.
Thanks Tim Graham for the report and Loïc Bistuer for the advices.
|