Tim Daniel schrieb: > > On 22 ene, 16:17, Thomas Guettler <h...@tbz-pariv.de> wrote: > >> Tim Daniel schrieb:> I read something that it would be more >> >>> efficient to store only the query and doing pickle?? I don't know how >>> to do that, I've been looking in the docs and other posts but no clear >>> explanation. So what I really want to know: which is the best way of >>> handling this problem? >>> >> I have my own paginator, too. >> > [snipped] > >> Thomas Guettler,http://www.thomas-guettler.de/ >> E-Mail: guettli (*) thomas-guettler + de >> > > Well the problem is not with the paginator itself(it works well), the > real problem is with the data to be displayed, it's about being > efficient to store data(like a queryset) in the request.session > variable. Does anybody know if this is the good way(I don't think so)? > And if it's not, which is the right way to handle this problem then? > > Sorry, I didn't say this in my last post: I don't store anything in the session for pagination. The query string (request.GET) is used to display the current result page. This URL can be stored in a bookmark or send to someone. The query gets evaluated on each request. The next pagination page gets the same GET dictionary, but "page_number" gets increased.
HTH, Thomas -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
