This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-16
Channels
- # aws (17)
- # babashka (2)
- # beginners (131)
- # bristol-clojurians (1)
- # calva (16)
- # chlorine-clover (6)
- # cider (10)
- # clara (5)
- # cljsrn (82)
- # clojure (176)
- # clojure-dev (14)
- # clojure-europe (13)
- # clojure-italy (13)
- # clojure-nl (4)
- # clojure-spec (10)
- # clojure-sweden (32)
- # clojure-uk (32)
- # clojuredesign-podcast (2)
- # clojurescript (34)
- # community-development (2)
- # conjure (17)
- # cursive (4)
- # datomic (51)
- # emacs (6)
- # figwheel-main (26)
- # fulcro (16)
- # graalvm (11)
- # jobs (2)
- # jobs-discuss (30)
- # kaocha (4)
- # meander (23)
- # off-topic (34)
- # pathom (5)
- # re-frame (10)
- # reagent (3)
- # reitit (6)
- # releases (3)
- # sci (36)
- # shadow-cljs (27)
- # sql (9)
- # testing (6)
- # tools-deps (28)
- # vim (8)
anyone know any tricks for doing pagination with datomic with pathom ( would like to do filtering and sorting too ) if i have to do in memory i can .. but its painful
the problem here is how to paginate datomic, they dont have a good solution, I spent a good time trying to get that to be efficient, but no good, the best I could do was paginate by date ranges, this way you can constrain space and make it usable (but has the trade-offs from date pagination, for example, the number of items for different date ranges may change dramatically)
thanks wilker .. will ponder some more then ..
If you're running your code on Datomic Cloud Ions or a Peer server doing the sort/pagination in memory is pretty close to order by/limit in SQL- it's happening in the database process. Consider using range queries, where possible. There's also a new index-pull API you should check out: https://docs.datomic.com/cloud/query/query-index-pull.html