Prevent creating databases with empty passwords #29
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
|
lgtm 👍 |
theMarix
force-pushed
the
bugfix/empty-passwords
branch
from
feafb1c to
0e5bf71
Compare
theMarix
force-pushed
the
bugfix/empty-passwords
branch
from
0e5bf71 to
8d515b6
Compare
treebee
approved these changes
May 8, 2018
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.
As issue #23 points out it is impossible to delete a database with an empty password. As, latest with Postgres 10, such databases become useless to any potential user anyways this code prevents creation of them. Thus, also solving the removal problem, at least for all future databases.