Klaudia Pałkowska

Added new property for long scenario duration in performance tests

    • -1
    • +1
    /performance/tests/approvedProductsForEssentialMedsAndDistrictHospital.yml
OLMIS-6566: Updated changelog

OLMIS-6566: Updated test duration for getting 9000 FTAPs and searching orderables by version identities

    • -1
    • +1
    /performance/tests/approvedProductsForEssentialMedsAndDistrictHospital.yml
You could extract checks for column names to the first method, and then use this method + other two checks in the second method and use it in the if statement. Or something like that https://review...

You could extract checks for column names to the first method, and then use this method + other two checks in the second method and use it in the if statement. Or something like that

OLMIS-6566: Removed unnecessary method from OrderableRepositoryImpl

It looks like it isn't. Moreover, the whole findOrderablesWithLatestModifiedDate method is unnecessary.

It looks like it isn't. Moreover, the whole findOrderablesWithLatestModifiedDate method is unnecessary.

OLMIS-6675: Added entity graph for Orderable with javax.persistence.loadgraph hint

OLMIS-6566: Renamed methods to better describe what they do

OLMIS-6566: Updated orderable search query
OLMIS-6566: Updated orderable search query
OLMIS-6566: Added constant for fullProductName string

OLMIS-6566: Refactored searching for orderables to use JPQL instead of native queries Also removed entity graph because it did not help with n+1 problem

OLMIS-6566: Added entity graph for Orderable

Please take a look at Sonar. It shows some issues and causes build failures.

Please take a look at Sonar. It shows some issues and causes build failures.

Why we need getQueryOrderableSearchParams method? Can't we just pass searchParams here as a parameter?

Why we need getQueryOrderableSearchParams method? Can't we just pass searchParams here as a parameter?

We shouldn't return date with hardcoded zone.

We shouldn't return date with hardcoded zone.

Please remove the comments.

Please remove the comments.

It was refactored to JPQL so I think we can use existing constants.

It was refactored to JPQL so I think we can use existing constants.

I think we wanted to get rid of native queries here. We can use JPQL like in other queries.

I think we wanted to get rid of native queries here. We can use JPQL like in other queries.

It should return ZonedDateTime.

It should return ZonedDateTime.

Raised up p90 for getting 10000 orderables to 55000ms

OLMIS-6566: Refactored some orderable queries to hql instead of native query

OLMIS-6566: Added district root entity result transformer and removed unnecessary distinct

OLMIS-6566: Changed native queries from OrderableRepositoryImpl to hql

Updated documentation for v3.7.0

    • binary
    /docs/source/releases/UI-Performance-3.7.png
    • -0
    • +236
    /docs/source/releases/openlmis-ref-distro-v3.7.0.rst
Prepared ref-distro for the next release

    • -1
    • +1
    /docs/source/components/erd-report.rst
    • -12
    • +12
    /docs/source/components/index.rst
Updated documentation for v3.7.0

    • -1
    • +1
    /docs/source/components/erd-report.rst
    • -12
    • +12
    /docs/source/components/index.rst
Updated services versions on demo-v3