docs: document connection string escaping rules (issue #140) - #197
Merged
Conversation
A connection string is processed by two independent parsers with
different escaping rules, which was undocumented and confusing:
1. The psqlODBC parser splits on ';' and '=' and uses braces {} (with
'}}' for a literal brace) or +/%XX percent-encoding to embed special
characters. Backslash is NOT special at this layer.
2. A pqopt value is handed to libpq, whose conninfo parser separates
parameters by spaces and uses backslash / single-quote quoting.
Document both layers in config.html and add connstring-escape-test, which
sets application_name through each mechanism and reads it back with
current_setting() to confirm the special character survives intact.
Reported-by: fjf2002
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A connection string is processed by two independent parsers with different escaping rules, which was undocumented and confusing:
Document both layers in config.html and add connstring-escape-test, which sets application_name through each mechanism and reads it back with current_setting() to confirm the special character survives intact.
Reported-by: fjf2002