Expose available_apps in django_db marker #1071
Merged
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.
Right now in a multi-schema environment, TransactionTestCases may fail to flush if there are foreign key dependencies between schemas because the test case will flush the DB in
_fixture_teardown(see source) but will not cascade truncation by default.I've encountered this issue in a multi-tenant environment, and another user has posted about a similar issue here.
Setting
available_appswill enableCASCADEduring truncation per the django docs (link)This PR exposes
available_appsso that this experimental feature ofTransactionTestCasecan be used inpytest-djangodirectly.Addresses #928