Disable PGUSER env when checking for existing database #380
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.
Alike for when pgx does CREATE DATABASE, this commit forces disabling of PGUSER when checking for existing database.
This failed on my test setup, since I had setup PGUSER (for other projects) but that caused
cargo pgx initto fail.There is no need to disable PGHOST / PGPASSWORD / PGPORT since that's being set at this point anyway (so they would override the env settings)