refactor!: move version from PostgreSQL::new() to Settings #82
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.
This PR makes significant changes to the way the PostgreSQL
Version
is managed. The version is moved intoSettings
to provide a consistent configuration approach. This also enables the version to be configured from a URL.API Changes
Settings.version: Version
postgresql_embedded::PostgreSQL::new(Version,Settings)
topostgresql_embedded::PostgreSQL::new(Settings)
postgresql_embedded::PostgreSQL.version()
postgresql_embedded::PostgreSQL::default_version()
postgresql_embedded::blocking::PostgreSQL::new(Version,Settings)
topostgresql_embedded::blocking::PostgreSQL::new(Settings)
postgresql_embedded::blocking::PostgreSQL.version()
Migration
If a specific version was being specified, then the code can generally change from this:
to this: