This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-21
Channels
- # aws (14)
- # babashka (35)
- # beginners (163)
- # boot (2)
- # calva (5)
- # cider (30)
- # clojure (143)
- # clojure-colombia (1)
- # clojure-europe (5)
- # clojure-nl (11)
- # clojure-spec (1)
- # clojure-uk (16)
- # clojurescript (71)
- # community-development (2)
- # conjure (1)
- # cursive (6)
- # datomic (30)
- # duct (4)
- # figwheel-main (11)
- # fulcro (28)
- # graalvm (3)
- # graphql (23)
- # hoplon (36)
- # jackdaw (24)
- # kaocha (16)
- # lambdaisland (1)
- # leiningen (4)
- # luminus (3)
- # meander (4)
- # observability (1)
- # off-topic (10)
- # pathom (5)
- # re-frame (27)
- # reitit (7)
- # remote-jobs (1)
- # sci (17)
- # shadow-cljs (22)
- # spacemacs (14)
- # sql (61)
- # testing (3)
- # tools-deps (27)
- # vim (2)
- # xtdb (18)
- # yada (2)
Hello everyone
Syntax error (Exceptions$IllegalArgumentExceptionInfo) compiling at (datomic_utils.clj:1:1).
:db.error/not-enough-memory (datomic.objectCacheMax + datomic.memoryIndexMax) exceeds 75% of JVM RAM
Did someone pass through this before when initialzing datomic?I wouldn’t even try to run a peer with less than 2-3g Xmx. There’s a lower limit where it won’t start at all, but I don’t remember where that ends up being
I increased heap memory
Still have this issue
I'm trying to find it
I resolved updating my java version
I had a too old java
I created a small Clojure lib/script to do (some of) the right things to upload a jar file to a S3 Maven repo. Folks using dev-local may find it useful. You can paste it into a bb script if you want it to go a bit faster. https://github.com/kennyjwilli/s3-mvn-upload
Does qseq lazily get all the entities? or is that eager and only the datomic/pull and xforms are lazy?
From the reading its eager
I take it he absence of a lazy datomic query means thats a very hard problem. As in if you can't get lazyiness on something involving joins (and not just an index).
I think you are assuming things that are not necessarily true
but I am not in a place of enough knowledge to answer definitively
conceptually, there is nothing about joining per se that prevents "laziness"
the qseq docstring at https://docs.datomic.com/client-api/datomic.client.api.html#var-qseq says "returning a lazy seq" ?
I believe qseq only performs the work in :find
(e.g. pulling) lazily. There’s still an eagerly realized query result set back there with all the values for the vars referenced by that find
When querying for an entity that contains a :db/valueType
of :db.type/ref
, what is the proper Datalog syntax for pulling attributes from the child entity? Does that have to happen as a two step query (i.e. pull the parent with the ref
value, then pull the attributes on that ref
entity that you want) or is there way to accomplish the fetching of attributes from a ref
entity in a single query?
@mafcocinco there are some examples in here (datomic cloud docs) https://docs.datomic.com/cloud/query/query-pull.html#orgdf2185f
thanks!