Remove db_pass escape logic #140
Merged
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.
We have had some infrequent complaints about DB_PASS not working at times. Unfortunately, the users who complain never provide any relevant detail that allows us to work to resolve the issue. The logic in this is to attempt to escape special characters in the password before feeding it into the database, the users who have the issue erroneously believe that db_password is the right var because of a lack of understanding, however, this does indicate that bypassing our escape logic is a potential solution. I did some testing with various passwords and had no issues by removing our escape logic at all.
If this works, we will want to replicate this PR to mariadb and other containers with a similar var and escape logic.