https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24027
Tomás Cohen Arazi <tomasco...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tomasco...@gmail.com
--- Comment #34 from Tomás Cohen Arazi <tomasco...@gmail.com> ---
Lets implement pagination as all the framework is completed to accomplish that!
No more Max items.
For references on using the API to render (paginated) datatables, see bug
20212. The important bits are embedding related objects for rendering and
filtering, and rendering properly :-D So you need to add embeds and build the
right renderers for each column.
Regarding my work on the performance front, I identified this situations:
- We retrieve (cached or not) the frameworks inside loops without a real need,
and really deep in the code. Take a biblio, as the outer situation: it only has
one framework assigned, we can pass it down to the last portion of the code we
call instead of doing it inside the loop (and many times as we do).
- The same applies for code related to OpacHiddenItems and friends. Bug 23247
is a good example of how I think it should be done. It might still need
fetching the framework outside now that I look at it with fresh eyes :-D
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
