Database always gets instantiated with correct settings #8
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
Database always gets instantiated with correct settings
Contributor
Author
|
We haven't heard back from you. Do you think this could be merged? |
Owner
|
Sorry for very very very late response. merged now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As part of the development on a new database project, we realized that setting the on_initialized parameter for a factory resulted in the other (database-related) settings being ignored.
This pull request addresses this issue. It is also related to tk0miya/testing.postgresql#18
If you have any comment or remark, we'll be happy to address those as part of this PR.
Thank you.