Is your feature request related to a problem? Please describe.
When users are migrating from clojure.java.jdbc to next.jdbc, they may have to change their code around the handling of what c.j.j allows as a "db-spec". Whilst next.jdbc supports the :dbtype/:dbname approach, it doesn't support :connection-uri or :datasource, even though it supports the values of those keys directly.
Describe the solution you'd like
It would be helpful to such users -- and projects such as https://github.com/yogthos/migratus for example -- if next.jdbc could accept these hash map formats and just "lift" those keys' values directly to be used.
Additional context
Recent discussions where this has come up:
Is your feature request related to a problem? Please describe. When users are migrating from
clojure.java.jdbctonext.jdbc, they may have to change their code around the handling of what c.j.j allows as a "db-spec". Whilstnext.jdbcsupports the:dbtype/:dbnameapproach, it doesn't support:connection-urior:datasource, even though it supports the values of those keys directly.Describe the solution you'd like It would be helpful to such users -- and projects such as https://github.com/yogthos/migratus for example -- if
next.jdbccould accept these hash map formats and just "lift" those keys' values directly to be used.Additional context Recent discussions where this has come up: