-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login fails when odbc_connect PWD= includes a plus sign #11250
Comments
pyodbc connector would appear to have been written as:
for decades. so we'd have to do something with that. likely would be very backwards incompatible for those who are working around this right now (Which you can do using an escape code for the + sign) |
Could we just document that the |
we could do that! |
but it looks like the current implementation is really wrong, is the thing. that unquote is likely left over from when the unquoting wasnt happening elsewhere. |
That is true. The string is now already unquoted by that point, so the |
right but....if someone is sending + sign like you are because they want a space character.... thiis would need LOTS of test cases |
Gord Thompson has proposed a fix for this issue in the main branch: Avoid removing + from odbc_connect parameter values https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/5248 |
Then the string would have to be completely manually quoted, and the
|
We need to have test cases both for string URLs that include We've yet to have any changes to URL of any kind that have not produced immediate blowback and arguments. |
Describe the bug
When
odbc_connect
is given a properly-formed ODBC connection string with a password that contains a plus sign, the plus sign is converted to a space and the login fails.Optional link from https://docs.sqlalchemy.org which documents the behavior that is expected
No response
SQLAlchemy Version in Use
2.1.0b1.dev0
DBAPI (i.e. the database driver)
pyodbc
Database Vendor and Major Version
MS SQL Server
Python Version
3.8
Operating system
all
To Reproduce
Error
Additional context
No response
The text was updated successfully, but these errors were encountered: