openlmis-referencedata

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
OLMIS-6470: Added validation for creating ReqGroup with already assigned SupNode + refactored SupervisoryNodeController + added error messages

OLMIS-6568 Fix file.format.incorrect message key in messages_en.

OLMIS-6450 Performance improvements and adjusting tests thresholds for FTAPs
OLMIS-6450 Performance improvements and adjusting tests thresholds for FTAPs
We can just ignore this error by: @SuppressWarnings("PMD.TooManyMethods");

We can just ignore this error by: @SuppressWarnings("PMD.TooManyMethods");

Please remove one of those changelogs (or merge them somehow).

Please remove one of those changelogs (or merge them somehow).

Extracting those lines to a separate method will cause "The class has too many methods, consider refactoring it" error while building project in Gradle.

Extracting those lines to a separate method will cause "The class has too many methods, consider refactoring it" error while building project in Gradle.

OLMIS-6470: Fixed creating and updating SupervisoryNode with RequisitionGroup
OLMIS-6470: Fixed creating and updating SupervisoryNode with RequisitionGroup
OLMIS-6470: Fixed creating and updating SupervisoryNode with RequisitionGroup

OLMIS-6450 Adjust performance tests thresholds fo FTAPs

    • -2
    • +2
    /performance/tests/approvedProductsForEssentialMedsAndDistrictHospital.yml
OLMIS-6450 Partition HQL queries to avoid StackOverflow

Hibernate is running into issues when a huge number of composite identities

is passed in the where clause. This wasn't a problem with native query, but

native query is slower and introduces n+1 loading problem. We partition

the identities to 3000 per chunk and merge the results.

Revert "OLMIS-6470: Testing if creating and updating a Supervidory Node with a Requisition Group works properly"

This reverts commit b84b42a9a76ba46a3ec688a9657932a95cac6fd5.

OLMIS-6470: Testing if creating and updating a Supervidory Node with a Requisition Group works properly

OLMIS-6470: Improved getUpdatedSupervisoryNode method - better log message and only one call

Ok, throwing exception here is not desired indeed. If we want to log a message, it should be changed to indicate that the Supervisory Node doesn't exist in the database.

Ok, throwing exception here is not desired indeed. If we want to log a message, it should be changed to indicate that the Supervisory Node doesn't exist in the database.

Could we merge those calls? I think we don't need the second one, we can simply return supervisory node object from the line 329.

Could we merge those calls? I think we don't need the second one, we can simply return supervisory node object from the line 329.

It's not checking whether SN exists in update request, but if a SN with a given id (as in the request) already exists. Throwing exception now may cause more trouble in the app's behavior if I am no...

It's not checking whether SN exists in update request, but if a SN with a given id (as in the request) already exists. Throwing exception now may cause more trouble in the app's behavior if I am not mistaken. The SN presence is validated before that and is indeed throwing ValidationMessageExeption if needed. Maybe I should just correct the log message as it's indeed confusing now?

OLMIS-6450 Retrieve last modified date only when needed

This means removing the response header with last modified date in search

and querying for it only when the if-modified-since header was provided

OLMIS-6450 Include ProgramOrderable and Programs in select query for orderables

OLMIS-6450 Avoid n+1 queries in orderables fetch

Including all necessary data in the native query

so that Hibernate doesn't fetch it 1 by 1.

I think we should add this message to MessageKeys and throw this message by ValidationMessageException.

I think we should add this message to MessageKeys and throw this message by ValidationMessageException.

OLMIS-6450 Attempt to improve performance of FTAP fetch

Attempting to avoid n+1 queries by joining necessary tables

in one query for Hibernate.