This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-07
Channels
- # aleph (1)
- # announcements (2)
- # babashka (1)
- # beginners (49)
- # calva (1)
- # cider (5)
- # clj-kondo (14)
- # cljdoc (11)
- # cljsrn (6)
- # clojure (120)
- # clojure-austin (1)
- # clojure-europe (6)
- # clojure-finland (3)
- # clojure-italy (29)
- # clojure-nl (6)
- # clojure-spec (38)
- # clojure-uk (14)
- # clojurescript (65)
- # code-reviews (8)
- # cursive (20)
- # data-science (1)
- # datascript (5)
- # datomic (57)
- # emacs (6)
- # figwheel-main (2)
- # fulcro (32)
- # funcool (1)
- # jackdaw (7)
- # jobs (3)
- # joker (7)
- # kaocha (8)
- # keechma (3)
- # nrepl (7)
- # off-topic (25)
- # quil (3)
- # re-frame (10)
- # reagent (43)
- # remote-jobs (1)
- # ring (1)
- # shadow-cljs (173)
- # sim-testing (1)
- # spacemacs (1)
- # sql (3)
- # tools-deps (34)
seems like the same issue there always is mapping lists to a relational model, and people do that all the time. I think I would abandon the vector, insert each part of the vector as a fact, and add some kind of join relation that tracks which list and what position in the list each item is in
I'm assuming you mean something like :modal/arg1
, :modal/arg2
, ... along with a :modal/numArgs
? I can see how you'd reconstruct the arglist, though I'm not sure what :db/type
you'd make the args in this case.
(FYI I ended up just serializing the :arguments to a Transit string. Some perf loss but acceptable for my use case.)
Say n is some member of the vector, have facts like [n :vector/member-of somenameoridforvector] and [n :vector/index somenumber]
And then you can have whatever other facts you want to store the actual value whatever that is
This is classic data normalization from SQL databases https://stackoverflow.com/questions/3070384/how-to-store-a-list-in-a-column-of-a-database-table