Koha/reports
Jonathan Druart e0d7ca0776 Bug 28804: (bug 25026 follow-up) Handle SQL errors in reports
Since bug 25026 DBMS errors are raised, but the report module is not
dealing correctly with the errors.
If an error occurred in execute_query, next queries will fail as well,
we should skip them.

Test plan:
1. Create report from SQL queries, containing errors (invalid syntax, etc.)
'SELECT id FROM borrowers' can do it
2. Execute the query
=> Without this patch you get a 500
=> With this patch applied you see that the error raised at DBMS level
is propagated to the UI
3. Confirm that there is no regression on valid queries

Signed-off-by: Owen Leonard <oleonard@myacpl.org>

Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>

Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>

Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
2021-08-13 07:28:41 -04:00
..
acquisitions_stats.pl
bor_issues_top.pl Bug 28523: Escape 'rank' in bor_issues_top.pl 2021-07-09 12:29:15 -04:00
borrowers_out.pl
borrowers_stats.pl
cash_register_stats.pl Bug 28264: (QA follow-up) Impliment fix for debit_type_code 2021-07-02 09:40:45 -04:00
cat_issues_top.pl Bug 28524: Escape 'rank' in cat_issues_top.pl 2021-07-09 13:44:43 -04:00
catalogue_out.pl
catalogue_stats.pl
dictionary.pl
guided_reports.pl Bug 28804: (bug 25026 follow-up) Handle SQL errors in reports 2021-08-13 07:28:41 -04:00
issues_avg_stats.pl
issues_stats.pl
itemslost.pl
itemtypes.plugin
manager.pl
orders_by_fund.pl
reports-home.pl
reserves_stats.pl
serials_stats.pl