Thanks for the help Evgenij

On Wednesday 22 May 2024 at 9:42:59 pm UTC+10 Evgenij Ryazanov wrote:

> Hi!
>
> mv.db files have two identical 4096-byte blocks in the beginning. You can 
> read one of them, discard trailing bytes 0x00, and convert previous bytes 
> to a string. This string contains comma-separated properties in the 
> name:value format. You can check value of the property format.
>
> 1 was used by old historic H2 1.4 or H2 1.3. There is no reliable and easy 
> way to determine a database version from their files. There is a CREATE 
> BUILD 196 or something like it in the file, 196 means H2 1.4.196.
> 2 was used by H2 2.0/2.1. Because H2 2.1.214 can read all these files, you 
> can safely pass 214 to Update utility.
> 3 is used by H2 2.2. H2 2.2.214 is able to read all these files and you 
> don't need to run the Upgrade utility in this case.
>
> Alternatively you can try to open the database file with the latest 
> version of H2 and check error message, if any. H2 throws a specific error 
> on an incompatible format, but in case of format 1 additional steps are 
> still required.
>
> Database files created by a non-release build of H2 should be used only 
> with the same build of H2. For example, H2 compiled from the current 
> sources also uses the same format 3, but its files aren't really compatible 
> with H2 2.2.
>

-- 
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/e76f38bb-64b4-41d3-9fc5-29561106ddc3n%40googlegroups.com.

Reply via email to