This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-30
Channels
- # adventofcode (27)
- # ai (1)
- # announcements (2)
- # aws (66)
- # babashka (2)
- # beginners (34)
- # calva (28)
- # cider (5)
- # clj-kondo (18)
- # clojure (16)
- # clojure-europe (4)
- # clojure-norway (2)
- # clojure-uk (3)
- # clojurescript (11)
- # code-reviews (23)
- # conjure (23)
- # core-logic (1)
- # cursive (12)
- # datalevin (1)
- # datomic (9)
- # introduce-yourself (3)
- # kaocha (3)
- # klipse (4)
- # malli (42)
- # midje (1)
- # minecraft (1)
- # missionary (4)
- # music (1)
- # nextjournal (10)
- # polylith (5)
- # re-frame (2)
- # reitit (1)
- # releases (1)
- # sci (126)
- # shadow-cljs (4)
- # sql (2)
- # tools-deps (11)
I'd like to have an attribute that is a boolean "flag" like "active" is there an idiomatic way? I was thinking to retract and assert the fact but it doesn't really fit I think because I want to show "inactive" in the ui. Do I use an attribute with "bool" value?
Adding the "active" property will also complicate all other business logic because you have to add another clause for it. On the other hand if you save history then the active property doesn't add data
I advise against using history for any domain information. Only use it for audit purposes.
It is not designed for that use case. Large perf penalties, constraints on what you can do. Valentin has a good post on this topic: https://vvvvalvalval.github.io/posts/2017-07-08-Datomic-this-is-not-the-history-youre-looking-for.html