This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-18
Channels
- # aleph (12)
- # beginners (31)
- # boot (67)
- # cider (17)
- # cljs-dev (14)
- # clojure (111)
- # clojure-dev (1)
- # clojure-france (4)
- # clojure-gamedev (1)
- # clojure-italy (49)
- # clojure-nl (3)
- # clojure-poland (2)
- # clojure-russia (18)
- # clojure-spec (15)
- # clojure-uk (68)
- # clojurescript (33)
- # core-typed (1)
- # datomic (15)
- # emacs (3)
- # graphql (4)
- # hoplon (36)
- # leiningen (3)
- # lumo (44)
- # mount (2)
- # off-topic (46)
- # om (21)
- # onyx (47)
- # parinfer (22)
- # pedestal (21)
- # protorepl (4)
- # quil (4)
- # re-frame (15)
- # reagent (4)
- # ring-swagger (9)
- # rum (27)
- # spacemacs (11)
- # vim (7)
- # yada (8)
@hlship: so with lacinia is there a way to avoid the N+1 query problem? Is it possible to use something like claro with it?
@rickmoynihan i haven’t tried but it should be possible with http://lacinia.readthedocs.io/en/latest/resolve/selections.html#previewing-selections
I am not familiar with Claro but looking at the README rapidly i assume it should be usable with Lacinia without trouble
@rickmoynihan alumbra is used in production at http://stylefruits.de I'm using it in another project with postgresql and I am very happy with it. If you implement the batch resolver protocol the SQL queries are efficient in my experience. Most of the time you don't have to deal with claro, alumbra handles all the projections for you. It's really fun to work with.