This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-28
Channels
- # adventofcode (2)
- # aleph (4)
- # announcements (3)
- # asami (13)
- # babashka (27)
- # beginners (74)
- # clj-kondo (18)
- # cljdoc (1)
- # cljs-dev (27)
- # cljsrn (5)
- # clojure (75)
- # clojure-australia (5)
- # clojure-europe (25)
- # clojure-uk (2)
- # conjure (1)
- # core-logic (1)
- # deps-new (1)
- # fulcro (13)
- # gratitude (8)
- # honeysql (1)
- # lsp (24)
- # missionary (45)
- # mount (2)
- # nextjournal (24)
- # off-topic (10)
- # pathom (5)
- # portal (3)
- # releases (1)
- # shadow-cljs (7)
- # specter (1)
- # tools-deps (1)
I have a question, I read the documentation, but maybe I don’t find what I want. I would like to create a similar query like at Datomic:
(d/q '[:find (pull ?m pattern) ...
if I understand good that is similar like
(mapv #(d/entity db %) (d/q '[:find [?m ...]
when I would like to get all records. Is that possible add a pattern for this like at Datomic..? (which extract the connected informations?)maybe connected to this https://github.com/threatgrid/asami/issues/126, so you can ignore my question
The pull API really is the most popular missing feature. I really need to get onto it soon. Unfortunately, I keep saying yes to requests to give talks, and that means that all my spare time is spent on that right now. For instance, I’m working on a talk right now.
Perhaps you should consider giving a talk about the upcoming Asami pull API support? 😁
Admittedly, I also let myself get sidetracked this week when I started building cljs-math
Just this morning I'd been benchmarking the https://github.com/tonsky/datascript/releases/tag/1.3.0.
> Pull [...] wasn’t performant. Up to the point where building pull tree manually using entities would outperform pull, even with all entities overhead. This seemed weird, because pull has much more information ahead of time, which could be leveraged for optimizations.
Specifically, the dominant use case for me would be pulling deep subtrees, and that's what I tested. I couldn't believe how well DataScript's pull
performed compared to Asami's entity
, about an order of magnitude faster. (And that's discounting the negative effect deeply nested trees have on Asami's entity
as previously discussed.)
Seeing as Asami is generally the fastest of Datalog databases (as far as I know), it would be exciting to see Asami's pull 🙂