This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-15
Channels
- # announcements (71)
- # architecture (2)
- # aws (41)
- # babashka (23)
- # beginners (80)
- # calva (26)
- # chlorine-clover (11)
- # cljfx (4)
- # cljs-dev (12)
- # clojure (78)
- # clojure-berlin (5)
- # clojure-czech (3)
- # clojure-dev (9)
- # clojure-europe (45)
- # clojure-france (16)
- # clojure-gamedev (2)
- # clojure-italy (3)
- # clojure-nl (4)
- # clojure-spec (8)
- # clojure-sweden (1)
- # clojure-uk (37)
- # clojurescript (18)
- # community-development (15)
- # conjure (30)
- # cursive (51)
- # datomic (16)
- # duct (19)
- # figwheel-main (3)
- # fulcro (23)
- # java (7)
- # jobs (2)
- # joker (10)
- # off-topic (7)
- # parinfer (1)
- # pathom (6)
- # reagent (5)
- # reitit (1)
- # remote-jobs (1)
- # sci (1)
- # shadow-cljs (55)
- # slack-help (3)
- # specter (4)
- # sql (21)
- # tools-deps (11)
- # vim (5)
- # xtdb (14)
I’m trying to disable some logging on a peer server that’s painfully verbose, but I can’t seem to make any progress with the docs. I have lein project that’s using datomic-pro
, tried to add a bin/logback.xml
but I’m not really sure how I actually configure datomic to pickup on that file (I added the slf4j exclusion so the datomic pro lib using logback), since I’ve changed all the loglevels to warn with no change in the verbosity. Also tried to use (.setLevel (org.slf4j.LoggerFactory/getLogger "datomic") ch.qos.logback.classic.Level/WARN)
with no progress. Let me know if there’s tips on how to disable the DEBUG
logging by default.
If you use the bin/run method of starting, it should have logback.xml on the classpath already
alternatively, you can include the -Dlogback.configurationFile= property to point to your own logback file
I got it, just wasn’t familiar with the convention. I added logback.xml
to my resources
dir so it’s in my class path, not using bin/run
, it’s a peer that’s also a server 🙂
Thank you
ah, ok. that’s different. I recommend always using the property btw instead of putting it on the classpath (except maybe in dev, where you can put the logback in dev-resources)
Yup, I’m on that page. I’ll add the property on deploy.
I'd like to write a :where
clause which will unify and bind a certain var if the relevant attribute is present, but which won't prevent the whole clause from matching if that attribute isn't present.
Something like this:
:where [?foo-id :foo/id "123"]
[?foo-id :foo/bar ?foo-bar]
Except I want it to match every :foo/id
of 123, regardless of whether :foo/bar
is present. But if it is present, I'd like to bind it to ?foo-bar
.
Is this possible?The key here is to understand what you're wanting this for. 9/10, you're actually just wanting to pull the field information out into ?foo-bar
For that, I would recommend using the pull syntax, ie.
Look for get-else
half way down: https://docs.datomic.com/on-prem/query.html @enn Could be a fit.