sql

All things SQL and JDBC...
emccue 2020-09-12T17:53:29.335100Z

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

emccue 2020-09-12T17:53:31.335200Z

emccue 2020-09-12T17:53:56.335600Z

emccue 2020-09-12T17:54:00.336100Z

running with lein test

emccue 2020-09-12T17:55:08.336300Z

emccue 2020-09-12T17:55:20.336900Z

but then in the repl

emccue 2020-09-12T17:56:01.337Z

emccue 2020-09-12T17:56:35.338100Z

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

emccue 2020-09-12T17:57:22.338300Z

emccue 2020-09-12T17:57:39.339Z

it just has a more confusing message

emccue 2020-09-12T17:57:53.339300Z

on account of the toString for that class

dharrigan 2020-09-12T18:53:54.339900Z

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.

emccue 2020-09-12T19:07:52.340300Z

oooooohhhhhh

emccue 2020-09-12T19:08:12.340700Z

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

seancorfield 2020-09-12T19:20:59.342600Z

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