This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-09
Channels
- # announcements (1)
- # aws (2)
- # babashka (3)
- # beginners (39)
- # calva (6)
- # chlorine-clover (20)
- # cider (9)
- # clojure (105)
- # clojure-australia (1)
- # clojure-europe (64)
- # clojure-france (2)
- # clojure-gamedev (2)
- # clojure-nl (10)
- # clojure-provo (1)
- # clojure-uk (21)
- # clojuredesign-podcast (1)
- # clojurescript (77)
- # clojurewerkz (2)
- # clojutre (1)
- # community-development (4)
- # conjure (13)
- # data-science (6)
- # datascript (10)
- # datomic (37)
- # fulcro (33)
- # graphql (23)
- # jobs (1)
- # luminus (2)
- # malli (12)
- # meander (2)
- # off-topic (42)
- # pathom (5)
- # re-frame (5)
- # reitit (3)
- # remote-jobs (6)
- # reveal (38)
- # shadow-cljs (2)
- # spacemacs (14)
- # specmonstah (1)
- # sql (8)
- # tools-deps (2)
- # vim (8)
- # xtdb (22)
Thanks for the session! And also, thanks for all the open source work beyond crux too! ๐
yes - stay tuned, we will post on here when @taylor.jeremydavid has post-processed
oh thank god dark mode. ๐
That's all very exciting stuff @taylor.jeremydavid et. al I look forward to playing with the new stuff
@victorbjelkholm429 (that ๐ฅ is me burning white backgrounds, btw...haha) i'm in northern india... it's sunny here too, but i can't look at white screens without getting an instant headache due to a bizarre eye injury. #darkmode4ever
wow, tomorrow-night-blue
instantly reminds me of editing basic files on the family 386
i've always loved zenburn but since the eye damage low-contrast is actually really hard for me to read. currently using some extremely cartoony monokai variant.
question about time and deleting in crux.
Assuming I have a key 123
with data at times t0
, t4
, t8
, if I transact a delete at t4
, the data at t4
disappears.
Is there a way to delete at, say, t2
and also delete the data at t4
and t8
and t(n >= 2)
?
(evicting 123
isnโt an option because we need to preserve everything prior to the t2
delete)
We don't have an API to do that in one step, but you can achieve the desired result by scanning through the entity history and deleting one by one (underneath the hood we'd still need to be doing the same kind of scanning anyway). The only downside of a non-native approach is the bloat in the transaction log for each delete op