Hi Thejaswi. A couple of suggestions:
Any reasons for having CommentFlag.flag being a string, and not a foreign key to a FlagType model ? Having them as strings makes it easier to end up with bad data (misspelling and so forth). Of course there is always the performance penalty, but it seems worth it. Also, many times it is useful to keep a "raw" body for a comment (as the user sent it), but also for performance reasons, a "processed" version such as html (from markdown or something else). Maybe keeping both in the db allows for speedier rendering. Then an application can define somewhere (maybe a settings) which function to process the comment (markdown, textile, some home made tag removing routine), and have that run and then persisting both at the database. Thanks Arthur --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
