This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-25
Channels
- # announcements (9)
- # asami (69)
- # babashka (151)
- # babashka-sci-dev (34)
- # beginners (90)
- # cider (21)
- # clj-on-windows (17)
- # clj-otel (4)
- # cljsrn (5)
- # clojure (27)
- # clojure-austin (3)
- # clojure-europe (87)
- # clojure-gamedev (1)
- # clojure-nl (3)
- # clojure-norway (8)
- # clojure-poland (2)
- # clojure-uk (3)
- # clojured (10)
- # clojurescript (50)
- # core-async (73)
- # cursive (28)
- # data-science (2)
- # datomic (17)
- # etaoin (1)
- # honeysql (6)
- # introduce-yourself (3)
- # jobs (1)
- # joyride (12)
- # malli (5)
- # nbb (14)
- # off-topic (18)
- # pathom (4)
- # podcasts-discuss (2)
- # polylith (30)
- # project-updates (3)
- # re-frame (33)
- # reitit (1)
- # remote-jobs (13)
- # shadow-cljs (59)
- # sql (12)
- # tools-build (7)
- # xtdb (36)
does the pull many api support sorting? i'm not seeing it in the pull pattern grammar but just wanted to double check
No. As far as i know the reason for this is that sorting in the db isnt more efficient (at least when using peer)
Yea it's more of a syntactic cleanliness issue for me. Would rather pack as much “logic” into the db queries as possible
Well, your app “is” the database when using datomic. Its doing the query-logic itself etc too. But i know the feeling 😅 have been searching for ways to support sorting / pagination in the past too
how does datomic find the classes for things like attribute predicates? I installed a predicate but it says it can't find my namespace.
Attribute predicates must be on the classpath of a process that is performing a transaction.
Does that mean it needs to be in the transactor ?
https://docs.datomic.com/on-prem/reference/database-functions.html#classpath-functions
i was looking for a quick way to stop a user from inputting like 20k characters into my API and then storing it in datomic. It seems that i'll have to rethink deployments and source code going this route. I'll just more tightly control the HTTP API. This is definitely interesting, but was not expecting to ever have to touch the transactor's container after starting it.
These checks should most likely be done in the peer-process, not the transactor. Also you can transact DB functions to the transactor if they are just using standard clojure/java.