This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-12
Channels
- # announcements (2)
- # architecture (1)
- # aws (22)
- # babashka (2)
- # beginners (39)
- # bristol-clojurians (2)
- # cider (1)
- # clj-kondo (12)
- # cljfx (75)
- # cljs-dev (16)
- # clojure (51)
- # clojure-berlin (1)
- # clojure-france (4)
- # clojure-nl (2)
- # clojure-norway (36)
- # clojurescript (5)
- # community-development (8)
- # data-science (1)
- # datomic (4)
- # emacs (4)
- # fulcro (7)
- # jobs-discuss (7)
- # juxt (1)
- # nrepl (3)
- # off-topic (38)
- # reitit (1)
- # ring (7)
- # sci (79)
- # shadow-cljs (5)
- # sql (15)
- # tools-deps (22)
- # uncomplicate (7)
- # vrac (1)
- # xtdb (18)
Getting some weird results that might not be next.jdbc's fault, but I'm not certain where to go from here debugging
this is the logic for making the connection - regardless of whether that logging-datasource call is there the first error happens
Not sure, but it's interesting that the stack shows clojure.java.jdbc
, and as far as I know, next.jdbc doesn't depend upon it.
At work we're slowly migrating from c.j.j to n.j so we have several namespaces that have both and since they both have an execute!
function in their primary API, that can be a bit confusing at times. There's also some overlap between c.j.j's primary API and next.jdbc.sql
so you have to watch out for that too. @emccue