Hey folks, I'm pleased to announce that beta4's https://github.com/xtdb/xtdb/releases/tag/v2.0.0-beta4 π
Highlights:
β’ PATCH / :patch-docs operation: upserts into XT, merging with any existing records and adding new ones where they don't already exist.
β’ Ops: we've been hard at work on XT's operational story - we've now got an additional deploy guide for https://docs.xtdb.com/ops/guides/starting-with-azure.html, as well as Prometheus metrics and shiny Grafana dashboards.
β’ Initial authn support through CREATE USER.
β¦ Separately, we're currently designing XT's authz with our design partners (bigger announcement to come when that lands) - please do <mailto:hello@xtdb.com|chime in> if you'd like to join the discussion.
β’ xtdb-jdbc library - helpers for use with Sean's excellent next.jdbc client.
As always, full details on the https://github.com/xtdb/xtdb/releases/tag/v2.0.0-beta4 - and, if we don't speak before, hope you all have a great Christmas and a happy and healthy 2025 π
James, Jeremy and the XT Team
Very niceβ¦ another common use-case neatly solved π
> PATCH / :patch-docs operation: upserts into XT, merging with any existing records and adding new ones where they don't already exist.
Does this mean that SQL UPDATE is more optimized now? Or is PATCH "just" a convenience?
@seancorfield PATCH also inserts if the entity in hand isn't present, so it's a different operation
(closer to SQL MERGE, but we haven't implemented that yet)
Ah, OK...