| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The change partly goes back to the old behavior for forwards migrations
which should reduce the amount of memory consumption (#24745). However,
by the way the current state computation is done (there is no
`state_backwards` on a migration class) this change cannot be applied to
backwards migrations. Hence rolling back migrations still requires the
precomputation and storage of the intermediate migration states.
This improvement also implies that Django does not handle mixed
migration plans anymore. Mixed plans consist of a list of migrations
where some are being applied and others are being unapplied.
Thanks Andrew Godwin, Josh Smeaton and Tim Graham for the review as well
as everybody involved on the ticket that kept me looking into the issue.
|
| |
|
|
|
|
| |
from unapplying the wrong migrations."
This reverts commit abcf28a07695a45cb5fb15b81bffc97bea5e0be3.
|
| |
|
|
| |
unapplying the wrong migrations.
|
| |
|
|
|
|
| |
__first__ works
Thanks to Chris Beaven.
|
|
|
migration tests.
Without this, we're unable to add actual migrations for the app.
|