fix: Do not save null values for TEAV [DHIS2-21599]

[enricocolasante]

Summary

Prevents the tracker importer from persisting tracked entity attribute values with a null/empty value, and enforces this at the database level by making trackedentityattributevalue.value NOT NULL. Previously, importing an empty value for an attribute that did not yet exist on the tracked entity inserted a meaningless row with a null/empty value instead of doing nothing.

Changes

• AbstractTrackerPersister.handleTrackedEntityAttributeValues: adds the isDelete && isNew branch so that sending an empty value for an attribute with no existing value is a no-op. Before this, valueChanged was true for new entries, so the empty value fell through to saveOrUpdateAttributeValue and inserted a row with a null/empty value.
• TrackedEntityAttributeValue.hbm.xml: marks the value property not-null="true", aligning the Hibernate mapping with the new DB constraint.
• New migration 2.44/V2_44_15__teav_value_not_null.sql: deletes any pre-existing rows where value IS NULL (legacy/orphan data — the encryption encryptedvalue column was already removed in V2_44_6), then applies ALTER COLUMN value SET NOT NULL. Empty string ('') is intentionally still allowed.
• TrackedEntityAttributeTest: adds two regression tests — one asserting that importing an empty value for an attribute not in the DB persists no row (isDelete && isNew), and a companion asserting that importing an empty value for an existing attribute deletes its row while leaving the others untouched (isDelete && !isNew).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
3 Accepted issues

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

See analysis details on SonarQube Cloud