Fork me on GitHub
#xtdb
<
2022-12-03
>
phill01:12:05

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}

refset09:12:34

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?

phill23:12:54

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?

refset00:12:15

h2 should work, but it's not something we've seen used in the wild a whole lot

refset00:12:19

updating the xtdb-jdbc module to use the latest version of h2 should be possible, but I don't think it's completely straightforward

refset00:12:25

if you have a mysql instance handy I'd probably opt for that (or Postgres 🙂)

refset00:12:55

I think the advantage of Postgres/MySQL in a single-user context is that you can scale up to multiple nodes (should that ever be needed) without having to stop/start