Reorder the user, password, host, port and database appearances for uniformity. #3207
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.
Hi,
Trying to add uniformity to the use of the keys (user, password, host, port and database) in the code and docs.
I see the use of fields scattered in code and in documentation, in many different orders. Figured it could help for clarity to try to have a similar as possible order. Makes it easier to see if you're forgetting one of them, identify changes, etc...
New to pg. Figured could be helpful. Thanks for a great package.
Fun fact (Had to check it out).
When you have 3 terms -> ternary.
when you have 4 terms -> quaternary. (ref.stack exchange discussion)