This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-24
Channels
- # announcements (2)
- # babashka (39)
- # babashka-sci-dev (1)
- # beginners (30)
- # biff (2)
- # cider (9)
- # clj-commons (5)
- # clj-yaml (30)
- # cljdoc (15)
- # clojars (1)
- # clojure (13)
- # clojure-europe (42)
- # clojure-poland (6)
- # clojure-uk (2)
- # cursive (4)
- # datomic (24)
- # graalvm (12)
- # graphql (7)
- # hyperfiddle (91)
- # lsp (175)
- # malli (3)
- # membrane (9)
- # music (1)
- # off-topic (5)
- # reagent (7)
- # reitit (1)
- # releases (7)
- # rewrite-clj (1)
- # scittle (7)
- # shadow-cljs (3)
Looking at the datascript example, it seems centered around pull. How feasible would it be to create "where" views, instead of just pulls?
Seems plausible. Is there any pull query that couldn't be expressed as a "where" view?
I guess I'm not totally sure what a "where" view is. Is that just using d/q
rather than d/pull
?
I think it should be possible either way.
Is the question whether or not datalog "where" views are expressive enough to get the required data or whether or not you can pass the necessary data to a membrane component and have it work?
On the membrane side, it shouldn't matter where the data comes from or where it's going. With respect to the expressiveness of datascript "where" views, I'm not an expert. Whats the focus on just the "where" part rather than the full datalog query?