Aller au contenu
For the complete DHIS2 documentation index, see llms.txt.

Notes de mise à jour de la version 2.35

⚠️ Please ensure you have read the upgrade notes from the PREVIOUS RELEASE, if upgrading from an earlier version

Base de données

  • Des opérandes d'éléments de données excessifs pourraient être créés en raison d'un problème de sauvegarde des tableaux croisés dynamiques. Ce script pourrait être exécuté afin de supprimer les opérandes d'éléments de données dépréciés qui empêchent la suppression des éléments de données. Pour plus d'informations à ce sujet, voir DHIS2-7043.

API

Fonctionnalité

  • L'application mobile J2ME est désormais désactivée et ne pourra plus fonctionner.

Applications

  • Une nouvelle application web de Configuration des SMS est désormais disponible. Cette application remplacera le module web Configuration mobile. Ce dernier module sera maintenu pendant un temps donné jusqu'à ce que l'ancienne application devienne stable.

Patch-specific Changes

2.35.2 Database Schema

  • New index on table trackedentityprogramowner over columns (trackedentityinstanceid, programid, organisationunitid). Improves lookup related to organisation unit scopes in the context of a program.
  • New index on table programinstance over columns (programid). Improves general lookup for programinstances based on program in most cases.
  • New index on table trackedentityattributevalue over columns (trackedentityinstanceid, trackedentityattributeid, lower(value)). This is in addition to the previous index over the columns (trackedentityattributeid, lower(value)). We saw situations related to value lookup in the context of tracked entity instances where postgres would revert to a sequential scan, when using the existing index would yield a much better result. With the new index we are successfully encouraging postres to use the index also when we are matching on tracked entity instances.
  • New index on table programstageinstance over the columns (status, executiondate). This table often grows a lot bigger than tracked entity instance and program instance tables, and we saw a bottleneck in some of our queries when including program stage instances as filters in searches. We added this index to improve the performance of the most common column we filter by, status, as well as executiondate, which is often used together with status when searching for events.

Caution

Due to the number of indexes, and the typical size of their tables, be aware that upgrading to this version or above might take a significant amount of time.