summaryrefslogtreecommitdiff
path: root/django/db/migrations/exceptions.py
AgeCommit message (Collapse)Author
2022-02-07Refs #33476 -- Reformatted code with Black.django-bot
2020-02-04Simplified imports from django.db and django.contrib.gis.db.Nick Pope
2017-12-28Removed unnecessary trailing commas and spaces in various code.Mariusz Felisiak
2017-02-28Refs #27656 -- Updated django.db docstring verbs according to PEP 257.Anton Samarchyan
2017-01-18Refs #23919 -- Removed python_2_unicode_compatible decorator usageClaude Paroz
2017-01-18Refs #23919 -- Removed encoding preambles and future importsClaude Paroz
2016-05-08Fixed #25945, #26292 -- Refactored MigrationLoader.build_graph()Jarek Glowacki
2016-04-05Fixed #25850 -- Made migrate/makemigrations error on inconsistent history.Attila Tovt
2016-03-10Fixed #26342 -- Prevented unpacking when repr a NodeNotFoundErrorJarek Glowacki
2015-09-19Fixed #24743, #24745 -- Optimized migration plan handlingMarkus Holtermann
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.
2015-05-13Fixed #24742 -- Made runserver.check_migrations ignore read-only databasesClaude Paroz
Thanks Luis Del Giudice for the report, and Aymeric Augustin and Markus Holtermann for the reviews.
2015-05-02Moved migration exception classes to shared moduleMarkus Holtermann
Thanks Aymeric Augustin for the review.