jdbcUrl is missing as replacement for backend and dbtype in config #8
Assignees
Labels
bug
Something isn't working
Comments
TimoKramer
added a commit
that referenced
this issue
Sep 16, 2020
next.jdbc can take urls via :jdbcUrl to configure your connection. For that to work it was necessary to make dbtype optional as configuration parameter and add jdbcUrl as optional configuration parameter. Now it is possible to pass the configuration partially as url and as key-value-pairs to configure the connection. - Closes #8 - Updated README
TimoKramer
added a commit
that referenced
this issue
Sep 17, 2020
next.jdbc can take urls via :jdbcUrl to configure your connection. For that to work it was necessary to make dbtype optional as configuration parameter and add jdbcUrl as optional configuration parameter. Now it is possible to pass the configuration partially as url and as key-value-pairs to configure the connection. - Closes #8 - Updated README - New CircleCI step for integrationtesting with postgresql and mariadb
TimoKramer
added a commit
that referenced
this issue
Sep 17, 2020
next.jdbc can take urls via :jdbcUrl to configure your connection. For that to work it was necessary to make dbtype optional as configuration parameter and add jdbcUrl as optional configuration parameter. Now it is possible to pass the configuration partially as url and as key-value-pairs to configure the connection. - Closes #8 - Updated README - New CircleCI step for integrationtesting with postgresql and mariadb
TimoKramer
added a commit
that referenced
this issue
Sep 17, 2020
next.jdbc can take urls via :jdbcUrl to configure your connection. For that to work it was necessary to make dbtype optional as configuration parameter and add jdbcUrl as optional configuration parameter. Now it is possible to pass the configuration partially as url and as key-value-pairs to configure the connection. - Closes #8 - Updated README - New CircleCI step for integrationtesting with postgresql and mariadb
TimoKramer
added a commit
that referenced
this issue
Sep 17, 2020
next.jdbc can take urls via :jdbcUrl to configure your connection. For that to work it was necessary to make dbtype optional as configuration parameter and add jdbcUrl as optional configuration parameter. Now it is possible to pass the configuration partially as url and as key-value-pairs to configure the connection. - Closes #8 - Updated README - New CircleCI step for integrationtesting with postgresql and mariadb
TimoKramer
added a commit
that referenced
this issue
Sep 17, 2020
next.jdbc can take urls via :jdbcUrl to configure your connection. For that to work it was necessary to make dbtype optional as configuration parameter and add jdbcUrl as optional configuration parameter. Now it is possible to pass the configuration partially as url and as key-value-pairs to configure the connection. - Closes #8 - Updated README - New CircleCI step for integrationtesting with postgresql and mariadb
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
next.jdbc is used under the hood and provides the option to pass a
jdbcUrlin the configuration map. It should be possible to configure jdbc with:jdbcUrlin the config-map.https://cljdoc.org/d/seancorfield/next.jdbc/1.1.588/doc/getting-started#the-db-spec-hash-map
The text was updated successfully, but these errors were encountered: