I see little benefit to this solution, having everything in one table is not necessarily a good thing.
There are a few drawbacks to this solution... - Relying on two fields in order to establish an association - Lack of flexibility. What happens when you decide that Blog comments need to have additional fields? - Poor normalization - Possibly meaningless fields for certain records (i.e. blog_comment_vote) for Image comment (which does not require any votes) On Sep 6, 5:43 am, luigi7up <[EMAIL PROTECTED]> wrote: > hola everyone, > > while developing application something crossed my mind. What about > organizing all comments throughout application in one database table. > > What I mean is this: > > If application has some kind of Blog, News, picture gallery you woul > create blog_comments table, news_comments table etc. > What about table creating one table that would hold all comments ?!? > Table comments would have following fields (id, model_name, item_id, > author, text) > > This table would get pretty huge very soon but there is some logic in > this approach :) > > What do you think? > > thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---