This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-08
Channels
- # asami (7)
- # aws (2)
- # babashka (21)
- # beginners (602)
- # calva (8)
- # cider (11)
- # clj-kondo (10)
- # cljfx (1)
- # clojure (177)
- # clojure-europe (43)
- # clojure-nl (3)
- # clojure-taiwan (2)
- # clojure-uk (45)
- # clojurescript (31)
- # depstar (8)
- # figwheel-main (2)
- # fulcro (12)
- # hugsql (2)
- # java (1)
- # jobs (2)
- # meander (1)
- # missionary (1)
- # off-topic (67)
- # other-languages (1)
- # pathom (212)
- # polylith (4)
- # rdf (1)
- # re-frame (10)
- # reagent (12)
- # reitit (28)
- # reveal (3)
- # shadow-cljs (21)
- # spacemacs (7)
- # sql (5)
- # tools-deps (12)
- # vim (1)
(sql/update! ds
:my-table
{:started-at (Instant/now)}
{:id id}
{:column-fn csk/->snake_case
:table-fn csk/->snake_case
:builder-fn rs/as-unqualified-kebab-maps})
returns
#:next.jdbc{:update-count 0}
Even thought I gave the builder-fn to return as maps. Why does this happen?@ashwinbhskr I'm not sure what you're asking here?
What do you expect to be returned here? An UPDATE
statement returns the number of rows affected.
> What do you expect to be returned here? An `UPDATE` statement returns the number of rows affected.
true, I should I have been clearer with my question.
I meant to ask why does it return a namespaced key word? instead of just {:update-count 0}
As the docs make clear, the "fake" result set returned in this case is not affected by the builder fn you specify.
👍 3