Fork me on GitHub
#sql
<
2019-09-06
>
pyr08:09:18

To follow-up on your question @seancorfield I am indeed considering it, the code predates next.jdbc and internally we have some bits to prepare our hikari-cp connections

pyr08:09:34

that being said, as long as next.jdbc and honeysql work together we're good

seancorfield08:09:37

Yup, the ["sql string" params] format is identical.

seancorfield08:09:02

And next.jdbc gives you namespace qualified maps by default, in case that is useful.

pyr08:09:37

definitely is

seancorfield08:09:34

Ping me if you have any questions about the migration. I'm trying to encourage everyone using clojure.java.jdbc to move to next.jdbc since that's where all future work will happen.

pyr08:09:50

seql does a lot of keyword qualification / unqualification

dharrigan15:09:51

honeysql and next.jdbc work wonderfully well together! 🙂