Getting some weird results that might not be next.jdbc's fault, but I'm not certain where to go from here debugging
running with lein test
but then in the repl
this is the logic for making the connection - regardless of whether that logging-datasource call is there the first error happens
it just has a more confusing message
on account of the toString for that class
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.
oooooohhhhhh
somehow i have both on my classpath and the ide auto imports the wrong one
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