Arthur de Jong

Open Source / Free Software developer

summaryrefslogtreecommitdiffstats
path: root/tests/migrations/test_executor.py
Commit message (Collapse)AuthorAgeFilesLines
* Fixed #24743, #24745 -- Optimized migration plan handlingMarkus Holtermann2015-09-191-0/+59
| | | | | | | | | | | | | | | | 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.
* Cleaned up docstring style, per Tim Graham review.Carl Meyer2015-06-041-7/+2
|
* Refs #24628 -- Added a second test and a docstring ↵Carl Meyer2015-06-031-0/+24
| | | | comment to avoid regression.
* Fixed #24628 -- Fixed applied status for squashed ↵Carl Meyer2015-06-031-0/+26
| | | | migrations.
* Refs #24264 -- Added failing test case for updating a FK ↵Markus Holtermann2015-02-161-0/+35
| | | | | | | | | | when changing a PK When the primary key column is altered, foreign keys of referencing models must be aware of a possible data type change as well and thus need to be re-rendered. Thanks Tim Graham for the report.
* Fixed #24184 -- Prevented automatic soft-apply of migrationsMarkus Holtermann2015-02-131-1/+9
| | | | | | | | | | | | Previously Django only checked for the table name in CreateModel operations in initial migrations and faked the migration automatically. This led to various errors and unexpected behavior. The newly introduced --fake-initial flag to the migrate command must be passed to get the same behavior again. With this change Django will bail out in with a "duplicate relation / table" error instead. Thanks Carl Meyer and Tim Graham for the documentation update, report and review.
* Sorted imports with isort; refs #23860.Tim Graham2015-02-061-2/+2
|
* Fixed #24129 -- Added indicator that migrations are ↵Markus Holtermann2015-01-121-1/+46
| | | | | | rendering the initial state Thanks Tim Graham for the review.
* Fixed #24123 -- Used all available migrations to ↵Markus Holtermann2015-01-121-0/+90
| | | | | | generate the initial migration state Thanks Collin Anderson for the input when creating the patch and Tim Graham for the review.
* Fixed #23745 -- Reused states as much as possible in ↵Claude Paroz2015-01-021-1/+1
| | | | | | migrations Thanks Tim Graham and Markus Holtermann for the reviews.
* Passed around the state between migrationsClaude Paroz2015-01-021-1/+1
| | | | Refs #23745.
* Replaced migration state render() by apps cached propertyClaude Paroz2015-01-021-1/+1
| | | | Refs #23745.
* Added another migration-executor test to avoid regressions.Carl Meyer2014-11-201-0/+35
|
* Fixed #23410 -- Avoided unnecessary rollbacks in related ↵Carl Meyer2014-11-201-1/+95
| | | | apps when migrating backwards.
* Revert "Fixed #23474 -- Prevented migrating backwards ↵Tim Graham2014-09-241-38/+0
| | | | | | from unapplying the wrong migrations." This reverts commit abcf28a07695a45cb5fb15b81bffc97bea5e0be3.
* Called table_names instead of get_table_list in migrationsClaude Paroz2014-09-231-4/+4
|
* Fixed some flake8 errors.Tim Graham2014-09-191-2/+2
| | | | | | Originally I added migrations to flake8 exclude because of long lines in migration files, but there are other directories named migrations we do want to check. We are not warning on line lengths yet anyway.
* Fixed #23474 -- Prevented migrating backwards from ↵valtron2014-09-151-0/+38
| | | | unapplying the wrong migrations.
* Revert "Fixed #23384 -- Allowed overriding part of a ↵Claude Paroz2014-09-051-1/+1
| | | | | | | | | dictionary-type setting" This reverts commit 66757fee7e921ad4c35e0b3f80c25e026100b31c. Discussions have led to think that this functionality does not bring significant benefits to justify the added complexity. Read also discussions on ticket #22734.
* Fixed #23384 -- Allowed overriding part of a ↵Claude Paroz2014-08-301-1/+1
| | | | | | | | dictionary-type setting This change is needed for upcoming changes where settings might be grouped in a parent dictionary. Thanks Tim Graham for the review.
* Fixed #23093: soft application detection for swapped modelsAndrew Godwin2014-07-251-2/+20
|
* Fixed #22881 -- Better soft_applied migration detectionChris Beaven2014-06-231-0/+14
|
* Removed usaged of contrib.sessions as a placeholder in ↵Tim Graham2014-06-161-10/+21
| | | | | | migration tests. Without this, we're unable to add actual migrations for the app.
* Remove overzealous migration flushes from migration test ↵Andrew Godwin2014-06-091-4/+3
| | | | suite
* Tests for #22325Andrew Godwin2014-05-091-0/+22
|
* Imported override_settings from its new location.Aymeric Augustin2013-12-231-1/+2
|
* Fixed #21302 -- Fixed unused imports and import *.Tim Graham2013-11-021-1/+0
|
* Fixed some flake8 issuesAlex Gaynor2013-10-301-1/+1
|
* Auto-apply initial migrations if their tables exist already.Andrew Godwin2013-10-301-13/+52
|
* Fix migration planner to fully understand squashed ↵Andrew Godwin2013-10-231-0/+53
| | | | migrations. And test.
* Fix some small errors in the testsAndrew Godwin2013-08-231-0/+5
|
* Fix weird planning issues when already fully migrated.Andrew Godwin2013-08-111-1/+33
|
* Add tests for the migrate command and fix a bug they exposedAndrew Godwin2013-07-251-0/+1
|
* Fix test running with new apps stuff/migrate actually ↵Andrew Godwin2013-06-191-0/+4
| | | | running migrations
* Add an Executor for end-to-end runningAndrew Godwin2013-05-301-0/+35