support for different nuget package name on PgServer constructor #23
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
…m the default "PostgreSql.Binaries.Lite" has been added.
mysticmind
reviewed
Feb 22, 2023
|
@mattiamerzi 2.1.0 is released, you can check the release notes here |
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.
package PostgreSql.Binaries.Lite is a bit old; last nuget version is dated back to 4/9/2019, providing PostgreSQL version postgresql-10.7-1.
In order to give the user the possibility to use a different postgresql version or distribution, I've added an optional constructor parameter to the PgServer class that pushes a different nuget package name to the Downloader.
The default behaviour is obviously unchanged.