3d96d91efb
SQL: fix handling of escaped chars in JDBC connection string (#58429) This commit fixes an issue emerging when the connection string URI contains escaped characters. The original URI is pre-parsed in order to re-assemble a new URI having the optional elements filled in with defaults. The new URI has been using however the unescaped query and fragment parts. So if these contained any escaped `&` or `=` (such as in the password option value), the unescaping would reveal them and make them later interfere with the options parsing. The commit changes that, so that the new URI be built from the unescaped "raw" parts of the original URI. (cherry picked from commit 94eb5a05e79c6e203de548d05b13e00295bd4489) |
||
|---|---|---|
| .. | ||
| client-apps | ||
| odbc | ||
| cli.asciidoc | ||
| index.asciidoc | ||
| jdbc.asciidoc | ||
| odbc.asciidoc | ||
| rest.asciidoc | ||
| translate.asciidoc | ||