#11465 - Limit case duplicate merging comparison based on creation da… #11734
Conversation
…te and archived status - removed disease index
|
SonarCloud analysis: https://sonarcloud.io/dashboard?id=SORMAS-Project&pullRequest=11734 |
| @@ -12320,4 +12320,10 @@ ALTER TABLE testreport_history ADD COLUMN dateofresult varchar(255); | |||
|
|
|||
| INSERT INTO schema_version (version_number, comment) VALUES (511, 'Add dateOfResult to TestReports #11453'); | |||
|
|
|||
| -- 2023-03-27 Limit case duplicate merging comparison based on creation date and archived status #11465 | |||
There was a problem hiding this comment.
Code linting fails because of these changes
There was a problem hiding this comment.
The error is received due to a misconfiguration of CICD pipeline.
leventegal-she
deleted the
feature-11465_limit_case_duplicate_merging_on_creation_and_archive
branch
|
@sergiupacurariu @leventegal-she Are you convinced that removing the index improves the query in general? My fear is that similar to my suggested improvment with the sub query, this only improves the situation for some data constellations but not for others. How big is the impact of removing this index? It looks like the index was added to improve a slow query for cases by disease for the dashboard when used with a lab officer (see #4307 (comment)). I don't think we should remove it wihtout checking this aspect. |
…te and archived status - removed disease index
Fixes #11465