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 don't believe there is a way to do this currently, so I believe this would fall more into a feature request than a question, but let me know if there is a way to do this with the current functionality.
Currently you can use both a connection string while still specifying some options like ssl, but other options like user or password don't appear to get merged (they're ignored) unless they're explicitly part of the connection string.
The alternative I have right now is preparsing the connection string into an instance of URL first, then manually setting url.user = 'user' and url.password = 'password', and then stringifying it before passing it into the client:
It'd be really nice for all the properties to "just work", while keeping the same behavior that anything defined in the connection string directly will take precedence.
The text was updated successfully, but these errors were encountered:
For complete safety, this would require us to parse the string into a URL, add the query params and then convert to a string. If you were not concerned with safety then
connectionString + '?user=my_user&password=my_password' is fairly terse.
I don't believe there is a way to do this currently, so I believe this would fall more into a feature request than a question, but let me know if there is a way to do this with the current functionality.
Currently you can use both a connection string while still specifying some options like
ssl
, but other options likeuser
orpassword
don't appear to get merged (they're ignored) unless they're explicitly part of the connection string.Works:
Doesn't work:
The alternative I have right now is preparsing the connection string into an instance of
URL
first, then manually settingurl.user = 'user'
andurl.password = 'password'
, and then stringifying it before passing it into the client:It'd be really nice for all the properties to "just work", while keeping the same behavior that anything defined in the connection string directly will take precedence.
The text was updated successfully, but these errors were encountered: