Can you elaborate on that? As I described in another recent post we plan to use at least two H2 versions (1.4.200 for legacy databases and 2.0.20x for all new ones) from the same application by using 2.0.20x in the application itself (embedded mode) and spawn a separate H2 TCP-server process that uses 1.4.200.
That means we will use 2.0.20x as the client for a 1.4.200 server. Is that not going to work? Or is backward compatibility from a newer H2 client to a (somewhat) older H2 version server likely? On Monday, 10 January 2022 at 10:03:49 UTC+1 Evgenij Ryazanov wrote: > Hello! > > You still have 1.4.195 somewhere. > > TCP protocol in H2 2.0.206 provides backward compatibility for 1.4.197 and > newer versions only. > > Client with 1.4.195 cannot connect to server with 2.0.206 and client with > 2.0.206 cannot connect to server with 1.4.195; these versions are too > different from each other. > > Normally you should have the same version of H2 on both client and server > side (or in all applications that use auto-server mode). > -- 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/98af5ba8-379f-4e07-8849-e7e694c8629en%40googlegroups.com.
