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
It turns out to be not a bug, but a feature :)
The keyword "Connect To Database Using Custom Params" was not supposed to work with pure connections strings / URI's, having all connection values in one string.
Instead, it Interprets the db_connect_string parameter value as a list of named arguments, which would be passed to the "connect" function of the selected db module. Example for psycopg2: database='my_db_test', user='postgres', password='s3cr3t', host='tiger.foobar.com', port=5432
So I left the keyword basically in the original state, just slightly improved the code and the docs.
But I've also added a new keyword Connect To Database Using Custom Connection String - it's designed to work with combined connection strings / URI's like this: postgresql://postgres:s3cr3t@tiger.foobar.com:5432/my_db_test
The following example would work:
But if you put no quotation marks around the connection string param, there is an error:
In order to avoid the backwards incompatibility, the code should be improved in the way that both options (with and without quotes) work.
Here is a full example for the oracle database:
The text was updated successfully, but these errors were encountered: