Add UsePostgres overload for data source configuration#35
Merged
Conversation
Adds UsePostgres(connectionString, configureDataSource) so users can tune connection pool size, timeouts, and other Npgsql settings without encoding them in the connection string.
|
This PR is included in version 1.22.0 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
UsePostgres(connectionString, configureDataSource)overload that exposesNpgsqlDataSourceBuilderfor tuning connection pool size, timeouts, multiplexing, and other Npgsql settingsBuild()UsePostgres(string)delegates to the new overload withnullCross-repo: part of the
perf/scalability-fixesbranch across Trax.Scheduler, Trax.Api, and Trax.Docs.Test plan
UsePostgreswith configure action doesn't throwUsePostgreswith configure action still registers DbContextFactoryUsePostgreswith null configure action matches default behavior