https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23626 --- Comment #22 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #21)
With the caching on the svc you can often see confusing results when testing JSON - I think using it in the GUI could give the same problem.
I think we could add some info to GUI to make it more clear how the caching operates and why you would set it.
Is it really such an issue that we should not allow people to get "all" if they explicitly check "all"? I think at least you'd want the GUI behave differently than a more restricted web service that might be used by third parties.
It is a big issue because loading a full set of results can crash the system. Reports with a large amounts of rows/data must be loaded into memory to pass to the template in either scenario. (DON'T) Try running: SELECT * FROM items JOIN biblio_metadata USING (itemnumber) JOIN items i ON 1=1; It generates so much data it will lock the system (mine required a hard reboot). This is a silly report, but honestly large reports that are legitimate in production systems are triggering this issue. Charts are neat, but I think we can limit the amount of data they get and rely on exporting to tools meant for data analysis if large scale are needed. -- You are receiving this mail because: You are watching all bug changes.