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
Hello,
Using the 0.4.3 version of KormaSQL I am unable to configure it to connect to a database that requires user credentials using the following query string:
Using the same connection-uri, I seem to be able to connect just fine using HugSQL (which uses Hikari instead of c3p0 pooling lib like Korma does). Is this something that would need to be added to Korma or is there problem elsewhere?
Thanks!
The text was updated successfully, but these errors were encountered:
Furthermore, passing the :user and :password in the config object to (postgres ) does not work, the connection still times out. The work around for now seems to be not to use the connection-uri and pass all (port host, db, user, password) in the object.
Edit: using another jdbc format: "jdbc:postgresql://dbuser:[email protected]:12001/dbname" also times out (which also works in the other library)
danielzurawski
changed the title
JDBC :connection-uri support for user and password query string
:connection-uri with user and password qs times out
Oct 14, 2016
Looking at code for 0.4.3, I don't see any support for connection uri. Can you post code examples how you have tried?
Support for connection uri has been implemented in commit 527565d (not released yet) and I believe it should support user and password in uri as well. However, I am not 100% as there are no tests for this and I haven't tried myself.
Hello,
Using the 0.4.3 version of KormaSQL I am unable to configure it to connect to a database that requires user credentials using the following query string:
jdbc:postgresql://172.16.100.2:12001/dbname?user=dbuser&password=password
Using the same connection-uri, I seem to be able to connect just fine using HugSQL (which uses Hikari instead of c3p0 pooling lib like Korma does). Is this something that would need to be added to Korma or is there problem elsewhere?
Thanks!
The text was updated successfully, but these errors were encountered: