On 5 tammi, 06:41, Vibhu Rishi <vibhu.ri...@gmail.com> wrote: > Hi Anssi, > > Thanks for the comment. > > I was thinking that if I have to do the last comment hackery for all the > objects would it also work if I > * add a last_comment_time field to the models I use with comments. > * modify the comment form ( not sure which file to modify, still thinking > it through) to add comment timestamp to the post model data. > > then the query could become much simpler in the sense that I only need to > get post objects, and sort by last_comment_time field.
This is likely the best approach for you. If you have an index on the last_comment_time field then db queries will be really fast. This is not the case for the view approach. In addition the view approach is complex and somewhat hard to maintain while the last_comment_time field is fairly straightforward to implement. I wouldn't do this on the form level. Instead I would do this in comment.save() (or post_save signal), or alternatively with a dedicated method for comment saving. If every comment is saved through that method then you know the last_comment_time will be correctly maintained. Of course, there are a lot of ways to do this, and they have different tradeoffs. Experiment and see what fits your purposes. - Anssi -- 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.
