This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-29
Channels
- # announcements (4)
- # architecture (1)
- # beginners (113)
- # boot (17)
- # calva (40)
- # cider (9)
- # clara (1)
- # cljs-dev (21)
- # cljsrn (21)
- # clojure (47)
- # clojure-dev (8)
- # clojure-europe (2)
- # clojure-italy (46)
- # clojure-nl (10)
- # clojure-spec (1)
- # clojure-turkiye (1)
- # clojure-uk (46)
- # clojurescript (102)
- # core-async (21)
- # cursive (35)
- # data-science (1)
- # datomic (7)
- # emacs (2)
- # graphql (1)
- # lumo (15)
- # nrepl (4)
- # nyc (1)
- # off-topic (5)
- # overtone (3)
- # pathom (10)
- # quil (6)
- # re-frame (30)
- # reagent (7)
- # reitit (33)
- # rewrite-clj (1)
- # shadow-cljs (37)
- # spacemacs (73)
- # test-check (3)
- # testing (2)
- # vim (59)
Is there any noticeable performance cost associated with using query rules vs. building the rules into the where clause?
How do I get the next chunk when using the async api? Whenever a take is made on the channel, the channel is then closed so I can't take again. Is this how to get the next chunk, through a succession of takes?
I had to add the :limit
option in order for it to not close the channel, although I am now getting an error of :cognitect.anomalies/unavailable ... Specified iterator was dropped
, what does that mean and can I do something about it?
@dogenpunk generally, yes, as we recommend you split your stack into independent storage and compute stacks as part of your first upgrade: https://docs.datomic.com/cloud/operation/upgrading.html