Why not do the additional manipulating *after* the paginator? If you want to do something before the paginator then you a) have to do it on all records, or b) limit it yourself in which case the paginator doesn't really have much work to do as you already limited the records yourself.
Just simply create the select object, pass it to the paginator, get back the needed 10/20/50/whatever number of records and do the additional work on them. On 9 April 2013 16:34, sinimix <[email protected]> wrote: > Hi Matus, > > Thank you for the answer. It's good and a valid way to display data in the > view helper, but let's forget author information for a moment and imagine > that we need to perform any other data manipulation before sending it to > the > paginator. The question was: Do I need to implement logic for limiting > results depending on the current page before the iterator is involved or > there is a simpler way? > > And one note, the paginator on my side is located in a controller and all > other methods are well organized (using your suggestion for view helper, > too). Example code I use in all discussions forums/topics are very simple > expressing the core idea in the simplest possible way trying to avoid > displaying several different methods and their relations. > > Thanks > > > > -- > View this message in context: > http://zend-framework-community.634137.n4.nabble.com/ZF2-How-to-use-paginator-with-huge-number-of-records-tp4659675p4659680.html > Sent from the Zend Framework mailing list archive at Nabble.com. > > -- > List: [email protected] > Info: http://framework.zend.com/archives > Unsubscribe: [email protected] > > > -- ~Robert Basic; http://robertbasic.com/
