This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-17
Channels
- # announcements (2)
- # aws (7)
- # beginners (46)
- # cider (15)
- # clj-kondo (24)
- # cljs-dev (3)
- # clojure (46)
- # clojure-dev (34)
- # clojure-europe (7)
- # clojure-italy (7)
- # clojure-nl (10)
- # clojure-norway (15)
- # clojure-spec (5)
- # clojure-uk (42)
- # clojuredesign-podcast (1)
- # clojurescript (79)
- # clr (3)
- # core-async (1)
- # cursive (45)
- # data-science (1)
- # datomic (4)
- # fulcro (17)
- # funcool (14)
- # gorilla (2)
- # graphql (30)
- # jackdaw (5)
- # jobs-discuss (8)
- # joker (4)
- # lein-figwheel (1)
- # off-topic (48)
- # pedestal (26)
- # re-frame (36)
- # reagent (18)
- # reitit (6)
- # remote-jobs (4)
- # shadow-cljs (115)
- # tools-deps (62)
- # vim (12)
I understand that this kind of question was asked a lot of time, but how to do a sorted pagination of complex objects in datomic cloud properly? By querying only ID's and sort-by fields, then sorting, dropping and taking a limit and, finally, pulling the entity with all nested fields and objects?
Do you want the pages to be against the same basis-t of the database? If so, you could separate the querying and sorting from the limit, dropping, and pulling. Then you could stick the sorted resulting eids in a cache somewhere and refer to it by some request guid. Generally I'd go with @U09R86PA4’s approach unless there is a special need for the caching approach above.