This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-07-12
Channels
- # announcements (2)
- # babashka (22)
- # babashka-sci-dev (15)
- # beginners (62)
- # calva (2)
- # cider (8)
- # clj-kondo (33)
- # clojure (52)
- # clojure-europe (46)
- # clojure-losangeles (1)
- # clojure-norway (5)
- # clojure-spec (7)
- # clojurescript (31)
- # conjure (20)
- # data-science (4)
- # datalevin (16)
- # fulcro (28)
- # hyperfiddle (71)
- # introduce-yourself (3)
- # lsp (50)
- # off-topic (16)
- # polylith (8)
- # portal (3)
- # practicalli (1)
- # reitit (1)
- # releases (2)
- # tools-build (22)
- # vim (8)
- # xtdb (17)
Heyo! Does juxt/site work with xtdb v2?
Cool! Any estimates on that?
Thanks for replies! site v2 will be warmly awaited. π Rock on, juxt team! :the_horns:
π XTDB Version 1.24.0
has arrived!
This release is focused on a number of enhancements to XTDB's checkpointing system. Checkpointing is an important concept for production deployments as it allows XTDB to scale out in a cluster and spin up new nodes quickly without having to replay the transaction log from the start each time on every node.
Release notes here: https://github.com/xtdb/xtdb/releases/tag/1.24.0
Thank you to everyone who helped us with designing and testing these enhancements π
FYI this link is broken on the docs https://docs.xtdb.com/clients/clojure/
Hey @U0HJD63RN thanks for mentioning that. Seems all 4 URLs on that page are affected :thinking_face: time to dust off the 404 link scanner...
I assume you found the right page(s) manually in the end but let me know if not or are otherwise struggling for info
https://github.com/xtdb/xtdb/blob/29fa08b921e0809f37469cbb40972daa4b88851c/modules/metrics/README.adoc#L8 another deadlink
XTDB v2 is absolutely one of my most highly anticipated pieces of tech in recent years, I've been playing around with it in some personal projects (where I would normally be throwing in a mysql database) and its been a very cool feel
Datalog at the moment, but I know my coworkers would often want to interact via SQL if anything ended up getting adopted
my only other datalog usage was a few projects that leaned on datalevin (usually some babashka scripts), so its not too foreign-feeling.
The biggest difference that I feel is definitely the shift from inserting maps with qualified keys, to inserting maps with unqualified keys into a "table". That and also the :xt/id
definitely threw me off at the start (didn't know how I should populate it), took me a bit to realize that it should just be the value of whatever my id
key was for the given data-structure, and it didn't need to be a value that was globally unique to everything in the database, just the table.
> one of my most highly anticipated pieces of tech in recent years we'd best get a wriggle on then @U050DD55V π