On Feb 7, 2:56 pm, Eric Abrahamsen <gir...@gmail.com> wrote: > On Feb 7, 2010, at 8:54 PM, eaman wrote: [CUT] > The lazy option would probably be to add get_next() and get_previous() > methods to your model, that return an instance based on whatever > definition of "next" and "previous" works for you. You might consider > some kind of timestamp field for your model, though – you'd be > surprised how often that comes in handy…
Thanks, I've made a try with the free pagination, which is nice and easy but doesn't work out of the box as I would like (but that's probbly me unable to pass an extra parameter to limit the query set...). I'm up to code those two methods, I guess I'll try first to embed them in the model and then to think about of some form of abstraction to use them with others similar models. Generic views are really nice, but I guess it's time for me to dive deeper in models and views. Thanks for the clue. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
