To be able to have new GeoModel nodes/classes while not breaking the load of DBs generated with an earlier version of GeoModel, I added an 'optional' flag to the calls loading the new nodes from the DB. In that way, when loading a DB where we don't expect to see those new nodes, we have no errors as expected.

To achieve that, I also added the optional flag to the 'checkDBTable' and 'getPublishedNodes' methods.

Riccardo Maria Bianchi authored 8 months ago and Vakhtang Tsulaia committed 8 months ago

Fixed UnidentifiedShape I/O (in particular, the restore part) and introduced a new unit test for GeoUnidentifiedShape writing and reading

Brought it in sync with Athena main version

Riccardo Maria Bianchi authored 8 months ago and Johannes Junggeburth committed 8 months ago

Due to a typo caused by copy-paste, materials' dataStart and dataEnd were set to same value because they were read from the same vector entry.

That resulted in building materials with exactly 1 element; which also involved the build into memory of only 1 element per material as well.

Riccardo Maria Bianchi authored 8 months ago and Johannes Junggeburth committed 8 months ago

Until you build the GeoModel tree, the caches are not created yet; however, the low-level methods can access the DB directly. So, the existance of a table should be verified at the DB level, not at cache level; otherwise the test fails when calling methods before building the GeoModel tree.