This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-26
Channels
- # announcements (17)
- # babashka (68)
- # beginners (8)
- # biff (14)
- # calva (25)
- # cherry (10)
- # clj-kondo (1)
- # clj-on-windows (12)
- # cljsrn (6)
- # clojure (134)
- # clojure-berlin (1)
- # clojure-europe (33)
- # clojure-nl (4)
- # clojure-norway (6)
- # clojure-uk (10)
- # clojurescript (9)
- # datalevin (8)
- # datomic (34)
- # docker (1)
- # emacs (31)
- # fulcro (6)
- # honeysql (8)
- # java (7)
- # joyride (14)
- # kaocha (7)
- # malli (11)
- # nbb (4)
- # off-topic (11)
- # pedestal (14)
- # rdf (53)
- # re-frame (6)
- # reagent (39)
- # reitit (2)
- # releases (9)
- # rewrite-clj (14)
- # shadow-cljs (97)
- # specter (1)
- # testing (5)
- # tools-deps (12)
- # vim (4)
- # xtdb (9)
Hey team, noob question. I was trying to understand how Datalevin caches requests to storage. https://github.com/juji-io/datalevin/blob/6dff73783a63aff353751d30a2287aa44c3ba8ea/src/datalevin/db.cljc#L101 Do I understand correctly, that the requests are cached at the pattern level? i.e if the query engine is trying to find relevant datoms for [?a :known-attr ?v], it will fetch all tuples with :known-attr as the attribute and cache this response.
Gotcha, thanks @U0A74MRCJ! Two follow-on questions: 1. If there’s a transaction, does it wipe the entire cache? 2. What happens if some results need to be paginated? (i.e the :known-attr tuples are too large to fit in memory)