-
Bug
-
Resolution: Unresolved
-
None
-
None
-
Critical
-
The event log of language resources did not use paging, leading to timeouts for language resources with a lot of log entries.
-
Emptyshow more show less
problem
The event log of language resources can hold big amount of data.
Currently the UI is not using paging there.
Also the DB indexes for the language resource log table and the task log table must be consolidated. Similar as it was done shortly for the main log table.
solution
Add paging to the event log of language resources in the UI
Consolidate the DB indexes for LEK_languageresource_log and LEK_task_log table, set the same indexes as they are in Zf_eventlog always + task|langres foreign key column