Thank you Evgenij, this is where a "Build ID" or "Commit ID" would become handy, packing into "h2-2.0.201_888e228.jar" instead of "h2-2.0.201" only. Also it wouuld be nice to be able to read that "Build ID" from the data base meta data or schema information (without opening the DB in full at the risk of corrupting it).
>From an end-users point of view, the H2 releases take very long and are massive. 201 has so many beautiful improvments (which fixed a lot of real-life production issues for us) that we rather follow the development as closely as possible even when 1.4.200 is declared stable. (At least in our experience, 1.4.200 is far less robust and correct than 2.0.201.) I will also have to figure out, how to support "Build IDs" in the Migration Tool, because following your advise we will have to export/create 20 H2 databases weekly. Best regards Andreas On Sun, 2021-02-14 at 16:51 -0800, Evgenij Ryazanov wrote: > Please note that database files created by one snapshot build should > not be opened with another snapshot build to avoid data loss or > corruption. Always export your data to SQL with your current build > and import it into new empty database with a new build if you want to > use a more recent (or older) build for a some reason. > -- > 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/29ca67ff-216c-4991-9da4-04271e79f964n%40googlegroups.com > . -- 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/d15c71206174c3c74d528aa38571100e2e65cb09.camel%40manticore-projects.com.
