Add support for using run_syncdb in unit tests on tenant schemas #556
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using django-tenant-schemas with Django 1.8, pytest-django works when using --no-migrations.
When upgrading to Django 1.10, existing tests for my project no longer work with --no-migrations, resulting in tests that take much longer to run.
The issue is Django 1.9 added the --run-syncdb option to the migrate command, which defaults to False. Looking at the migrate source code, the --no-migrations functionality requires run_syncdb to be True in order to work correctly.