mmm so I could use Post model with a foreign key to blog and a Comment model with a generic foreign key ( because I could comment post, images, videos, ecc ). Is this a wrong ? What is the better solution in your opinion ? Thanks ^_^
--------- On 25 Mag, 13:32, Tom Evans <tevans...@googlemail.com> wrote: > On Tue, May 25, 2010 at 12:20 PM, nameless <xsatelli...@gmail.com> wrote: > > Generic field because on my project you can post and comment in Blogs, > > Gallery pages, Foto pages, video pages, ecc. > > So I want to use my Post_comment models for post and comment > > anythings. > > Is this a wrong solution ? > > Are there problems with the performances ? > > > Thanks ;) > > Well, GFKs aren't cheap (or rather, can be expensive). > > It depends whether you think that galleries/photos/videos have > posts/comments (m2m from gallery/photo to post/comment), or that > posts/comments are associated with any object (GFK). > > The GFK allows you to easily find the object associated with a > post/comment. The m2m approach allows you to easily find the comments > associated with a particular object. > > Cheers > > Tom > > -- > 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 > athttp://groups.google.com/group/django-users?hl=en. -- 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.
