Clojurians Log v2

No need to use hikari-cp - next.jdbc supports Hikari out of the box, no wrapper needed.

Make a connection pooled data source. Use with-options to wrap it if you want global options baked in (but I don't recommend that - I recommend using the default and just getting used to qualified keywords).

If that doesn't help, you'll need to share code to show folks what you're trying, and be more specific about "doesn't work" 😁

Yeah I am using ->pool and I tried wrapping the pool call and get-connection calls using with-options, but when I do that I get an error saying "No matching field found: close for class next.jdbc.default_options.DefaultOptions".

Also, i'm curious what your reasoning is for recommending qualified keywords is that just to avoid conflicts? I don't like how verbose it would make all the keyword map accesses.

They're idiomatic. You can use aliases and/or destructuring to make code shorter. But, frankly, I think they help clarify the code and don't really add much burden, especially when your editor can provide auto-suggest for keywords. As for your errors, I'd have to see code to help more.

It seems the error is coming from use of with-open should I still be using that even when using a connection pool?

And yeah I know there are idiomatic, that is why I think I should look into them further. I just know it would be a mess to migrate over to using them now on our project since its quite big and would break in many places. We have a full test suite but still would be quite the migration. Not sure it would be worth it for us at this time.

with-open is fine with get-connection with Hikari. We use that all the time at work. As I said, without seeing code, I can't tell what you're doing wrong.