This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-17
Channels
- # announcements (6)
- # beginners (117)
- # calva (22)
- # cider (7)
- # clara (56)
- # clj-kondo (8)
- # cljdoc (3)
- # cljfx (26)
- # clojure (58)
- # clojure-czech (2)
- # clojure-europe (20)
- # clojure-greece (1)
- # clojure-india (7)
- # clojure-nl (11)
- # clojure-uk (100)
- # clojurescript (48)
- # conjure (24)
- # cursive (117)
- # data-science (3)
- # datascript (5)
- # datomic (33)
- # emacs (29)
- # figwheel-main (3)
- # fulcro (12)
- # jobs (1)
- # malli (40)
- # parinfer (4)
- # pathom (1)
- # quil (2)
- # re-frame (17)
- # reagent (20)
- # reitit (1)
- # reveal (97)
- # ring (5)
- # shadow-cljs (11)
- # spacemacs (12)
- # sql (4)
- # tools-deps (18)
- # xtdb (25)
@seancorfield Snowflake support’s response about the getGeneratedKeys() returning an empty result set that has null for metadata. Related to discussion a couple weeks ago
> Engineering and I have reviewed it and in our perspective, it is an expected behaviour. The reason behind getMetadata() returning null for an empty result set is because no metadata exists for type EmptyResultSet. So, technically we do implement the getGeneratedKeys() function; there are just never any keys.
Well, I'd say they're categorically wrong based on the JDBC spec but, hey, next.jdbc "supports" their weird behavior now so... 🤷:skin-tone-2:
Thanks for the follow-up tho'...