multidb: let one connection be reused, and other not #74
Conversation
This file contains hidden or 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
|
Hi @mahomahomaho, thanks for this report and patch. I am working to make database setup in pytest-django generally more flexible, to make customizations like this very easy, without adding custom settings or command line options. I made a note about this in #128. There will hopefully be some progress with regard to this during the EuroPython sprints and I will give an update after the sprints. |
…into reuseperconn Conflicts: pytest_django/db_reuse.py
|
Closing as per previous comment. |
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.
set per settings.py
instead (besides) of set --reuse_db in cmdline, I can set TEST_REUSE in db setting, which let me reuse one db (postgres in this case) , which is big and expensive to create/copy, and create other (small sqlite).