https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38822
--- Comment #24 from Matt Blenkinsop <[email protected]> --- Created attachment 210285 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210285&action=edit Bug 38822: Add a counter log summary API GET /erm/counter_logs/summary lists the erm_counter_log_summary table through the read-only Koha::ERM::EUsage::CounterLogSummary class, with the usual q, _order_by and paging parameters. The table does not store the provider name: embed usage_data_provider with x-koha-embed, and search or order on usage_data_provider.name. erm_counter_log_summary is a derived table. Koha::ERM::EUsage::CounterLogSummaries->rebuild writes the rows of one provider, report type and year from erm_counter_logs, and takes a lock on the provider as the jobs of its months run in parallel. Koha::ERM::EUsage::CounterLog calls it in store and delete, for the key of the log and, when a stored log moves to another provider, report type or year, for its old key. So every writer of counter logs keeps the summary right. A counter log written with plain SQL needs a call to rebuild. The migration script of Bug 41307 calls it after it backfills the counter logs. Assisted-by: Fable 5.1 (Anthropic) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
