You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched (google, github) for similar issues and couldn't find anything
I have read and followed the docs and still think this is a bug
Bug
This bug-fix #3061 introduced percent encoding for the query attribute of AnyUrl. It lists a set of characters that get percent encoded and refers to the url-spec.
According to the url-spec, the + character is in the group of safe characters and should not be encoded (page 16 in the doc).
As a consequence of the introduced characters encoding, my database connection string to a MS SQL Server DB got unusable:
Checks
Bug
This bug-fix #3061 introduced percent encoding for the
query
attribute ofAnyUrl
. It lists a set of characters that get percent encoded and refers to the url-spec.According to the url-spec, the
+
character is in the group of safe characters and should not be encoded (page 16 in the doc).As a consequence of the introduced characters encoding, my database connection string to a MS SQL Server DB got unusable:
Output of
python -c "import pydantic.utils; print(pydantic.utils.version_info())"
:It would be cool to have a MSSQLServerDsn similar to Postgres, Redis, or MongoDB instead of the general AnyUrl (https://pydantic-docs.helpmanual.io/usage/types/#urls).
The text was updated successfully, but these errors were encountered: