Fork me on GitHub
#sql
<
2020-09-12
>
emccue17:09:29

Getting some weird results that might not be next.jdbc's fault, but I'm not certain where to go from here debugging

emccue17:09:00

running with lein test

emccue17:09:20

but then in the repl

emccue17:09:35

this is the logic for making the connection - regardless of whether that logging-datasource call is there the first error happens

emccue17:09:39

it just has a more confusing message

emccue17:09:53

on account of the toString for that class

dharrigan18:09:54

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.

emccue19:09:52

oooooohhhhhh

emccue19:09:12

somehow i have both on my classpath and the ide auto imports the wrong one

seancorfield19:09:59

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