This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-03
Channels
- # adventofcode (23)
- # announcements (2)
- # babashka (54)
- # babashka-sci-dev (2)
- # beginners (14)
- # biff (5)
- # calva (25)
- # cherry (9)
- # clj-kondo (4)
- # clojure-europe (2)
- # clojure-japan (2)
- # clojurescript (1)
- # data-science (6)
- # datascript (3)
- # datomic (1)
- # dev-tooling (25)
- # etaoin (5)
- # events (5)
- # hyperfiddle (1)
- # nbb (2)
- # off-topic (27)
- # shadow-cljs (1)
- # xtdb (7)
With h2 updated to version 2.x, there is something unexpected in Xtdb: #error { :cause org.h2.api.TimestampWithTimeZone ... {:type xtdb.IllegalArgumentException :message Error locating module :data {:xtdb.error/error-type :illegal-argument, :xtdb.error/error-key :error-locating-module, :xtdb.error/message Error locating module, :module xtdb.jdbc.h2/->dialect}
Hi @U0HG4EHMH I'm not sure we've attempted upgrading and tested with 2.x so far. Are you hoping to use h2 for some specific reason?
The case is single-user data processing. h2 is already part of the environment (and thus also the hope to use a recent version of it). I'm trying it because programs operate in so many settings that the abstruse JVM options would be a chore and "native code" seems like a shortcut to disaster. Is h2 very regrettable with xtdb? Would mysql (hosted elsewhere) do better?