jGnash 2.34.1 Release Issues with users of Relational Databases

[Craig Cavanaugh]

If you are using the xml or bxds file formats, this issue does not impact you.

The latest update of jGnash has broken compatibility for users of the H2 relational database.  Skip to the Recovery Options if you don't care about the technical mumbo-jumbo.

A few releases ago, the database schema was updated.  This was due to Hibernate evolving and incrementally improving compatibility with the JPA standards.  

Up to this point, jGnash was able to support the old database schema and new database schema transparently.  If the old schema was used, it was never forced to the new schema.  H2 was impacted the most and with recent updates, additional changes have broken old schema files.

Expect a similar issue with relational databases for the next jGnash 2.35.0 release.  Additional Hibernate changes are coming that will break all relational database files.  A new schema will be used that will result in a minor performance improvement, improved JPA compatibility, and less database schema complexity.  The same recovery process with be used as well.

Recovery Options:

1. Open the last backup file (extract the XML file from the zip backups that jGnash created automatically using the default configuration options).  From there, continue to use the XML file as it, or save back to H2 or one of the other file formats.
2. Roll back to the prior jGnash release, and save the file as a different file type and open it in jGnash 2.34.1. 

Thanks,

Craig Cavanaugh