Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I developed a like/dislike vote system.
Pretty simple, a vote table where there are article_id, vote_type (-1 or +1)
Two avoid such SELECT SUM(vote_type) FROM vote WHERE vote_type = +1 I had the idea to store that count in my article table using an Event/Listener system.
What do you think about that?
This type of doing things (denormalization) is a very standard practice when performance is much more important than data integrity. So IMHO it’s more than OK to do it in your case, as you don’t really care if the “like” count for a page becomes slightly off for some reason.
However, you might need to store the likes one-per-row anyway if you want to also save information such as who liked what, timestamps, etc. Which in no way invalidates what I said in paragraph above.