This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-20
Channels
- # beginners (17)
- # boot (19)
- # chestnut (1)
- # cider (25)
- # clara (1)
- # cljs-dev (15)
- # cljsrn (10)
- # clojars (9)
- # clojure (182)
- # clojure-brasil (27)
- # clojure-dusseldorf (2)
- # clojure-gamedev (5)
- # clojure-germany (1)
- # clojure-greece (2)
- # clojure-italy (18)
- # clojure-poland (5)
- # clojure-romania (3)
- # clojure-russia (29)
- # clojure-serbia (6)
- # clojure-spec (9)
- # clojure-uk (77)
- # clojure-ukraine (1)
- # clojurescript (61)
- # cursive (5)
- # datomic (20)
- # defnpodcast (1)
- # emacs (10)
- # fulcro (2)
- # graphql (2)
- # hoplon (11)
- # lumo (4)
- # off-topic (50)
- # om (3)
- # onyx (26)
- # other-languages (39)
- # parinfer (2)
- # pedestal (5)
- # re-frame (32)
- # reagent (48)
- # rum (7)
- # shadow-cljs (10)
- # spacemacs (29)
- # sql (10)
- # unrepl (58)
- # vim (3)
Hi - have a clojure.jdbc query. We are using result-set-seq, and for a particular query it becomes very slow going trying to move past the next fetch-size of results. We tried to set the timeout opt, but I suspect this only impacts the initial query, not the scrolling through of results, is this correct?
Can you share some code so we can see how you're setting up the RS and what you're trying to do with it?
not easily. It's a prepared statement. I'm not keeping hold of the seq head coming from the query, I'm iterating over it in a doseq and feeding the results onto some core.async channel
What is :fetch-size
set to?
(have you tried smaller / larger values to see if makes a difference?)
Also, given the setup with a PreparedStatement, have you tried raw Java interop to eliminate java.jdbc
itself as a cause?