Bug 17120 - Specify number of rows per page in report and initial run
Summary: Specify number of rows per page in report and initial run
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Reports (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
: 34496 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-08-12 18:15 UTC by Christopher Brannon
Modified: 2024-02-14 20:49 UTC (History)
7 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2016-08-12 18:15:27 UTC
I think we could enhance reports so that the &limit= parameter could be initially set with the report settings and stored in a field in the table.

I also think we could have the drop down available on the parameters page when running the report the first time.

If you have a report you know that would run well and could be completely shown with more rows, why not have the option to initially set it differently than the default?

The LIMIT command in SQL is okay and works for actually limiting the total number of results, but does weird things if you specify a number larger than 20.  The results still span multiple pages, plus it doesn't give you options while running like this would.
Comment 1 Andrew Fuerste-Henry 2020-11-05 17:00:08 UTC
+1, this would be handy when one has a report that consistently gives, say, 24 results. It gets really tiresome to have to expand the results each time the report runs.
Comment 2 Cab Vinton 2020-11-05 19:10:05 UTC
+1. Not only that, but I believe the entire report is re-run whenever changing the number of results per page. Not particularly efficient when dealing with more complex queries.
Comment 3 Katrin Fischer 2023-08-08 15:14:25 UTC
*** Bug 34496 has been marked as a duplicate of this bug. ***