This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-18
Channels
- # architecture (25)
- # beginners (57)
- # boot (3)
- # cider (38)
- # clara (6)
- # cljsrn (6)
- # clojure (54)
- # clojure-china (4)
- # clojure-greece (1)
- # clojure-italy (3)
- # clojure-romania (1)
- # clojure-russia (7)
- # clojure-spec (68)
- # clojure-uk (46)
- # clojurescript (73)
- # community-development (2)
- # core-async (7)
- # cursive (17)
- # datomic (143)
- # duct (2)
- # emacs (12)
- # events (5)
- # figwheel (3)
- # fulcro (15)
- # hoplon (19)
- # jobs (12)
- # jobs-discuss (85)
- # nginx (3)
- # off-topic (111)
- # onyx (7)
- # other-languages (1)
- # re-frame (30)
- # reagent (19)
- # remote-jobs (1)
- # ring (7)
- # rum (1)
- # shadow-cljs (18)
- # spacemacs (4)
- # specter (4)
- # sql (24)
- # test-check (1)
- # unrepl (10)
- # vim (6)
- # yada (1)
I’ve been attempting to use the onyx-sql plugin with the task upsert-rows
on a Postgres database and I don’t think it supports it.
I’m not a database expert, so maybe there’s something I’m missing, but from what I understand, Postgres requires some extra “ON CONFLICT” portions in the query to support upserting.
Ah, that was recent user contributed functionality, so we won’t be able to provide much in the way of information there.
If you can find a way to make it support both (possibly with a flag), that’d be great.
My current plan was checking for the subprotocol of the sql-settings and if it is “postgresql” make the changes to the query necessary.
That’d be fine 🙂