You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As more and more data gets imported into the current alpha-test environment there has been a huge negative impact on the overall performance of the platform. This in part is a problem of the design of the Allocation entity, which is to huge and includes to many fields that should better be entities on their own e.g. the indication codes.
Describe the solution you'd like
Move fields that should better be an entity on their own to new entities and link them to the Allocation entitiy. Other then that it seems reasonable to create a AllocationListQuery that returns an AllocationListDto only including fields nescessary of the list view of the allocations.
Describe alternatives you've considered
I guess there is none...
Additional context
Entities that should exist on their own might be:
Indication (code)
Occasion
Assignment
Speciality / Speciality Detail
Infections
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As more and more data gets imported into the current alpha-test environment there has been a huge negative impact on the overall performance of the platform. This in part is a problem of the design of the Allocation entity, which is to huge and includes to many fields that should better be entities on their own e.g. the indication codes.
Describe the solution you'd like
Move fields that should better be an entity on their own to new entities and link them to the Allocation entitiy. Other then that it seems reasonable to create a AllocationListQuery that returns an AllocationListDto only including fields nescessary of the list view of the allocations.
Describe alternatives you've considered
I guess there is none...
Additional context
Entities that should exist on their own might be:
The text was updated successfully, but these errors were encountered: