The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Rating system, best solution?

As of now it's like this, I have one table where I store the score, total rates and what movie was rated, I also have an extra table where I store the user id and the movie id to keep track of which users have rated the particular movie(s).

This works fine and all but would this solution be better:

Add and extra column to my "main" table, let's name it "raters", and when a user rates a movie I insert their username or id there.
I would then use explode to get the users and see if they had rated the movie.

What would be better performance wise? Let's say we are dealing with 50.000 users (not the case) What is better, Have 50.000 rows in the keep-track-table or have 50.000 users(a lot of text/numbers ex: 1|2|412|2837918|1212) in the extra field "raters"?

Then you can perform the calculations on the movie's score every time somebody wants to see it... mysql will cache the results so you don't have to worry about your computer performing the same calculation again and again...

It seems a little easier way of organizing and maintaining the information...
And on top of that, you can add a "review" column or something to the end of table2, allowing users to make quick comments regarding a movie..