This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-14
Channels
- # aws (6)
- # babashka (31)
- # beginners (69)
- # biff (9)
- # boot (9)
- # bristol-clojurians (1)
- # calva (20)
- # chlorine-clover (2)
- # cider (8)
- # cljsrn (24)
- # clojure (25)
- # clojure-norway (4)
- # clojure-spec (29)
- # clojure-uk (7)
- # conjure (23)
- # datahike (5)
- # datomic (39)
- # emacs (4)
- # fulcro (4)
- # graalvm (11)
- # honeysql (1)
- # lambdaisland (1)
- # leiningen (8)
- # liberator (1)
- # libpython-clj (3)
- # malli (6)
- # mxnet (1)
- # off-topic (94)
- # pedestal (13)
- # re-frame (4)
- # releases (2)
- # shadow-cljs (8)
- # spacemacs (22)
- # sql (9)
- # vim (1)
Is next.jdbc a superset of Clojure.java.jdbc?
@neo2551 https://cljdoc.org/d/seancorfield/next.jdbc/1.0.462/doc/readme#motivation
I consider it the 1.0 release that I was never going to be able to do with c.j.j
is it a bad idea to insert 11k rows into a postgres table with next.jdbc? I am reading values from a json file, and I want to get them into a table.
We have a DB setup script at work that loads about 100k rows into MySQL via JDBC (I can't remember whether that part of our system uses c.j.j or next.jdbc right now). We don't run it very often. I wouldn't say it's necessarily a good idea or a bad idea.
Ok, this is just local work, I was wondering if this sort of batch processing should be avoided.
"it depends" 🙂
of course it does 🙂
I did want to say thanks for your work on this, its very nice to work with full on sql + clojure objects