Model I've described is just an example. In the real world, I'm developing imageboard (chan). This is anonymous forum with sections. Each section needs to have its own post counter. It is very typical for all modern chans (wakaba, kusaba etc.). Wakaba just creates separate table for each section, what is very inefficient.
And what is 'hardest solution'? I've thought about mutexes. On Feb 10, 2011, at 2:34 PM, Tom Evans wrote: > The easiest solution is to not do this. What purpose does it serve? If > you wish to order the posts in the order in which they were made, > simply record a created timestamp on the post model, and order them > appropriately. If you wish to know the total number of posts in a > thread, use aggregation to count them. -- 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.
