On Sun, 25 Oct 2009 12:41:25 -0400 Bob Waycott <[email protected]> wrote:
> With all due respect, handling pagination at the template level is > NOT a good idea. This is offering a pretty lazy way to create > paginated product listings. Also with all due respect, the OP asked for an example of how to paginate the results. I gave an example. If someone asks a question on the users list about pagination a suggestion that "You could write a custom view" could be considered a little less than helpful. > > Templatetags (which is what django-pagination is) should be used to > do minor presentation-focused manipulations of data returned from a > view. They should not be given the task of performing logic-related > manipulations of said data. Pagination is presentation. I don't have a back to back comparison but if the OP has, say, 12 items and he wants 4 per page doing it that way won't make much of a difference either way. > > The reason "there doesn't seem to be a performance hit using > django-pagination" is that you're not using a big enough result set > and you are using a wrong metric of evaluation. Very insightful of you. You will know then that I have a test database of more than 20,000 items with categories averaging around 2,000. This is a real dataset taken from a real ecommerce site running on a different platform currently. I don't know how many items the OP is using and I suspect you don't either. In any website, but particularly ecommerce, performance is always one of the most important metrics. Regards, Iain. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
