This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-03
Channels
- # aleph (2)
- # announcements (13)
- # babashka (7)
- # beginners (36)
- # calva (26)
- # cider (11)
- # circleci (13)
- # clj-kondo (15)
- # clojure (105)
- # clojure-europe (79)
- # clojure-nl (3)
- # clojure-uk (6)
- # clojurescript (17)
- # conjure (4)
- # core-logic (2)
- # cursive (10)
- # data-science (5)
- # datalevin (11)
- # datalog (14)
- # eastwood (6)
- # emacs (2)
- # figwheel-main (1)
- # fulcro (34)
- # google-cloud (1)
- # graphql (3)
- # introduce-yourself (7)
- # jobs (1)
- # leiningen (17)
- # lsp (46)
- # malli (2)
- # minecraft (3)
- # missionary (19)
- # off-topic (31)
- # other-languages (49)
- # polylith (2)
- # portal (5)
- # practicalli (1)
- # quil (77)
- # releases (1)
- # remote-jobs (1)
1000 storage calls, but one storage call may return lots of data, or little bit of data
in the future, we can also specify the size by bytes, but it will be more complicated to implement
Will you be incorporating https://github.com/tonsky/datascript/releases/tag/1.3.0 improvements to pull
?
Eventually. We have not even finished feature parity with Datascript 0.8.3 yet. This particular improvement should be easy to incorporate, maybe simply copy the code over? PR welcome.
Most of these Datascript improvements are easy to incorporate, for they sit on top of IDB abstraction. Most of Datalevin’s work is below that and doesn't change too much things above it. Even after our query engine rewrite, the pull part would remain the same as Datascript
Thanks, that is good to know. I'm not familiar with the code base, so I'll have to find some time to take a closer look.
these types improvements also make a great case for a clojurists together application https://www.clojuriststogether.org/open-source/
these types improvements also make a great case for a clojurists together application https://www.clojuriststogether.org/open-source/