This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-16
Channels
- # announcements (3)
- # babashka (25)
- # beginners (71)
- # calva (18)
- # clj-kondo (52)
- # cljs-dev (94)
- # cljsrn (12)
- # clojure (33)
- # clojure-europe (52)
- # clojure-nl (2)
- # clojure-uk (27)
- # clojurescript (18)
- # clojureverse-ops (4)
- # datomic (64)
- # deps-new (27)
- # depstar (5)
- # events (5)
- # fulcro (5)
- # graalvm (12)
- # graalvm-mobile (82)
- # helix (2)
- # introduce-yourself (1)
- # juxt (5)
- # lsp (10)
- # malli (7)
- # missionary (1)
- # off-topic (41)
- # pathom (69)
- # pedestal (6)
- # re-frame (4)
- # reagent (8)
- # releases (9)
- # remote-jobs (8)
- # shadow-cljs (3)
- # sql (46)
- # tools-deps (44)
- # uncomplicate (1)
- # vim (83)
Hey there. I'm curious about how crux interacts with your new sql layer. I understand that you can configure column names as either strings or keywords, correct? Is that a meaningful difference when it comes to doing a sql query? For instance will I SELECT column_name
or SELECT :column_name
if the column is inserted as a keyword?
As per https://opencrux.com/reference/1.17.1/sql.html#table-definitions you'll do SELECT column_name
or SELECT table.column_name
even if the attribute is a keyword. Since you still have to ingest with EDN, it's probably wise to keep the attributes as keywords, regardless. I'm not actually sure if string attributes are supported — I've never seen anyone try to do that.
Perfect, thank you
It's probably worth noting you're likely to get faster replies (to Crux questions) from a wider audience in #crux or Zulip, btw. 🙂