Hey @U04V70XH6, welcome 👋 We expose an open-q function which returns a Closeable Iterator of results - idiom is as follows:

(with-open [res (crux/open-q db '{:find ..., :where ...})]
  (->> (iterator-seq res)
       ...))

I was hoping there was something that exposed a reducible context, but I guess I can wrap open-q up in one (after all, that’s what clojure.java.jdbc and next.jdbc do under the hood).

Funnily enough we just opened a PR to add IReduceInit to open-q today 🙂 would that be sufficient? https://github.com/juxt/crux/pull/1477/files

I'd err on the side of us not merging that PR as it stands, FWIW - but certainly an idea for future API development

an external wrapper to open-q (as opposed to wrapping the result of open-q) would probably be a better shout, as @U04V70XH6 suggested

I mean, wrapping the result works, as the test suggests, but it might not guarantee everything that the next.jdbc equivalents do - particularly, the ability to reduce multiple times over the same plan

If you plan to do resource management via IReduceInit, it should be in charge of opening the resource (as well as closing it) — not just close it at the end.

Since open-q already does the opening of the resource, you can’t make its result directly reducible. You need a wrapper.

Right, yep 🙂

It was a great talk! And it’s why I’m here and playing with Crux 🙂