On Sep 6, 4:48 pm, teknoid <[EMAIL PROTECTED]> wrote:
> 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)
FWIW I disagree.
A comment is a comment a vote is something else. if a system has
comments on several different objects and their structure is the same
(title, user_id, body) it makes no sense to me to have duplicate
tables. If their structure is not the same it probably means the name
of the model doesn't depict what it is (like trying to merge ratings
and comments ans still calling it "comment").
AD
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
