This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-12
Channels
- # beginners (58)
- # boot (4)
- # calva (1)
- # cider (13)
- # cljdoc (1)
- # cljs-dev (7)
- # cljsrn (14)
- # clojure (93)
- # clojure-canada (1)
- # clojure-conj (1)
- # clojure-germany (1)
- # clojure-italy (6)
- # clojure-losangeles (3)
- # clojure-nl (8)
- # clojure-spec (6)
- # clojure-uk (77)
- # clojurescript (3)
- # cursive (5)
- # data-science (6)
- # datomic (52)
- # emacs (1)
- # figwheel-main (2)
- # fulcro (6)
- # graphql (7)
- # jobs (9)
- # leiningen (1)
- # luminus (15)
- # mount (14)
- # off-topic (94)
- # pedestal (1)
- # re-frame (7)
- # reagent (10)
- # shadow-cljs (75)
- # spacemacs (4)
- # test-check (15)
- # tools-deps (23)
- # unrepl (1)
@currentoor i don't know why i put atom on there, i change my entire code, and start using ident, and then this working, thank you so much!
:thumbsup:
What's the best way to handle large tables? Following one of fulcro examples, I've a PersonList of Persons, and there are thousands of them on the server. So I'm gonna grab them in manageable chunks, were the ui is just a window into what's on the server, but I'll also have metadata based on the approach, total records, page num/size, hasPrev/Next, etc. Do I just stick say :person-list/has-next true
in the db?