This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-04
Channels
- # architecture (9)
- # babashka (33)
- # beginners (53)
- # biff (3)
- # cljdoc (11)
- # clojure (8)
- # clojure-austria (2)
- # clojure-dev (9)
- # clojure-europe (64)
- # clojure-nl (2)
- # clojure-norway (49)
- # clojure-sweden (4)
- # clojure-uk (4)
- # clojurescript (16)
- # cursive (14)
- # datahike (31)
- # datalevin (6)
- # datascript (9)
- # events (1)
- # fulcro (4)
- # honeysql (8)
- # hyperfiddle (116)
- # introduce-yourself (1)
- # kaocha (2)
- # malli (13)
- # nyc (2)
- # off-topic (4)
- # polylith (5)
- # portal (1)
- # reagent (1)
- # reitit (18)
- # releases (1)
- # spacemacs (6)
Hey! Why does index-range
only support :avet
? I have a :db.cardinality/many
:occurrences
that are instants and I want to get the instants that fall in a range for an entity. I can use seek-datoms
with :eavt
and then use take-while
to ensure that I only consume while it's still the desired entity and attribute. index-range
seems like the more appropriate function. It would be perfect if I wanted all :occurrences
inside of a range but I only want to query for one entity.
I see that both index-range
and seek-datoms
call slice under the hood. So, it indexes the b-tree to get the starting datom and walks from there.
Well. I guess one answer is that that's how datomic works. https://docs.datomic.com/client-api/datomic.client.api.html#var-index-range