Thank you for your quick reply and advise. Indeed, different versions of JDBC make any sort of backporting feel like an overwhelming task in the short term.
Regarding the old version of H2 that has worked for me so far - the problem is that I'm trying to migrate off it due to a bug which I've been unable to fix. I think that for the time being, I will put renewed effort into fixing the old bug. If I get it fixed, I have no pressure to migrate to 2.0 and can wait for Android to reach somewhere with its development. Evgenij Ryazanov kirjutas esmaspäev, 26. aprill 2021 kl 06:56:48 UTC+3: > Hello. > > Android is far behind regular Java, some its parts, especially the JDBC > API are still somewhere on Java 6 level, so you cannot use current H2 on > this platform, it is not supported by H2 any more. > > Android API 26 got various significant improvements for better > compatibility with Java 7 and 8, but not in the JDBC area. Current H2 > requires at least JDBC 4.2. It was released 7 years ago with Java 8, but > Android still doesn't support it and has many other limitations. Java 8 by > itself is not a problem if you don't support very old devices, but various > missing Java APIs used by non-Android libraries, including the H2, is the > real problem of this platform. > > The simplest solution there is to use some old release of H2 that works > for you. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/55c06b09-19c9-4466-ba51-5df686669f0fn%40googlegroups.com.
