Hi John and Don, I guess the root cause in the data types mismatch between table schema and actual data at the store or type of the query parameter. To explore the gap, it would be very handy if you could provide a small reproducer (standalone project or PR somewhere).
> In my case I'm not even using UUID fields. Also the same code 2 diff > environment dev vs prod doesn't cause the issue. I'm lucky enough that it's > on dev and prod is ok. > > But that last part might be misleading because in prod I think it happened > early on during upgrade and all I did was recreate the sql table. > > So before I do the same on dev... I want to see what the issue is. > > On Tue., Aug. 2, 2022, 6:06 p.m. , <don.tequ...@gmx.de> wrote: > >> I‘m only speculating but this looks very similar to the issue I had last >> week and reported to the group here. >> >> Caused by: org.h2.message.DbException: Hexadecimal string with odd number of >> characters: "5" [90003-197] -- With best regards, Taras Ledkov
