This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-02
Channels
- # adventofcode (63)
- # announcements (21)
- # babashka-sci-dev (1)
- # beginners (24)
- # biff (2)
- # calva (78)
- # cherry (6)
- # clj-commons (3)
- # clj-kondo (7)
- # clojure (91)
- # clojure-austin (2)
- # clojure-bay-area (6)
- # clojure-denmark (1)
- # clojure-europe (45)
- # clojure-nl (1)
- # clojure-norway (16)
- # clojure-portugal (3)
- # clojure-uk (1)
- # clojurescript (20)
- # conjure (11)
- # datalevin (13)
- # datomic (5)
- # emacs (14)
- # etaoin (15)
- # events (7)
- # fulcro (9)
- # funcool (1)
- # honeysql (26)
- # joyride (4)
- # kaocha (3)
- # lambdaisland (2)
- # malli (7)
- # off-topic (22)
- # pathom (29)
- # portal (58)
- # practicalli (8)
- # rdf (25)
- # reagent (14)
- # sci (3)
- # scittle (37)
- # shadow-cljs (10)
- # slack-help (2)
- # spacemacs (7)
- # sql (7)
- # tools-deps (1)
- # xtdb (2)
what's the standard way in jdbc to set the database to use? i use hikari-cp for connection pooling and i was surprised that the mariadb adapter doesn't seem to support the databaseName option
next.jdbc
builds a JDBC URL (which includes the database name) and sets the jdbcUrl
property in HikariCP in next.jdbc.connection/->pool
@UAEH11THP
Looks like hikari-cp
supports that approach too via :jdbc-url
?
next.jdbc.connection/jdbc-url
accepts a db-spec hash map (with :dbname
etc) and will return a JDBC URL you could use with hikari-cp
's :jdbc-url
property.
HikariCP itself has a databaseName
property but I don't know whether it works for all drivers. Sounds like that's what you're running into with the hikari-cp
wrapper and MariaDB?