fix: Use org unit stored path [DHIS2-18234]

[larshelge]

Introduces a new method getStoredPath() on OrganisationUnit.

Note that the path property is mapped with the "property access" mode in Hibernate. Per the Hibernate docs:

Property access mode implies the JPA provider accessing the entity’s state through its getter and setter methods. These methods can be used for encapsulation and additional logic as well.

This means that Hibernate will call getPath() and set the path property as part of all persistence operations. This in turn means that we don't have to recalculate the path value in the DHIS 2 application every time we need the value, as it will be persisted in the database.

The exception is when code modifies the ancestors/parents and relies on an up-to-date path value. Though in those special cases, one can simply call the getPath() method. In all other scenarios, the getStoredPath() method can be called, which should introduce a significant performance gain.

For the getStoredPath() method, if the path is not defined, typically as part of an integration test where the state is not yet flushed to the database, the calculated path based on the org unit ancestors is returned.

Reducing the pressure from re-calculating the path may alleviate the problem of DHIS2-18234 where the UID of the ancestor org units are not reflecting the persisted value.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
9.9% Duplication on New Code

See analysis details on SonarQube Cloud