Bug 40893 - Item Search - Display All entries is dangerous
Summary: Item Search - Display All entries is dangerous
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching (show other bugs)
Version: Main
Hardware: All All
: P5 - low trivial
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-29 07:57 UTC by Mathieu Saby
Modified: 2025-10-07 13:19 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Saby 2025-09-29 07:57:06 UTC
In Item Search, the selector "Display ... entries" above the results can be set to "all". 
If there are a lot of items, it can generate an error.

This "all" should be hidden, or maybe displayed only if there are less than xxx (1000?) items to display.
Comment 1 Mathieu Saby 2025-09-29 07:57:46 UTC
See also https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40815
Comment 2 Anneli Österman 2025-10-02 06:54:27 UTC
If the maximum number of rows are limited, there should be possibility configure it. For example 1000 rows is a bit low number when you are doing batch edits. Background jobs allows you to modify bigger batches that 1000 so it would be unfortunate change if the amount is limited to 1000 by default.
Comment 3 Katrin Fischer 2025-10-05 13:07:11 UTC
It also works well for more than 1.000 items in most cases. For most our libraries "all" works and can be useful. If a limit is proposed, it should be configurable.
Comment 4 Jonathan Druart 2025-10-07 13:19:10 UTC
The only correct way to implement this need is to implement a generic solution, in the table settings.

We already have "Default display length", we could have a "Max Length", or even a multi select for each table with the different options (10, 20, 50, 100, 500, all).

Preferably on top of bug 38259.