Home/ Questions/Q 293855
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T06:18:49+00:00

If we look at the stackoverflow website we have votes. But the question is

  • 0

If we look at the stackoverflow website we have votes. But the question is what is the bestway to store who has voted and who has not. Lets also simplify this even more and say that we can only vote Up, and we can only Remove the Up vote.

I was thinking having the table to be in such form

question - Id(INT) | userId(INT) | title(TEXT) | vote(INT) | ratedBy(TEXT)

Thre rest is self explanitory but ratedBy is a Comma Seperated Id values of the Users.

I was thinking to read the ratedBy and compare it with the userId of the current logged in User. If he dosent exist in the ratedBy he can vote Up, otherwise he can remove his vote. Which in turn will remove the value from ratedBy

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think to make another table “vote” is better. The relationship between users and votes is n to n, therefore a new table should be created. It should be something like this:

    question id (int) | user id (int) | permanent (bool) | timestamp (datetime)

    Permanent field can be used to make votes stay after a given time, as SO does.
    Other fields may be added according to desired features.
    As each row will take at least 16B, you can have up to 250M rows in the table before the table uses 4GB (fat32 limit if there is one archive per table, which is the case for MyISAM and InnoDB).
    Also, as Matthew Scharley points out in a comment, don’t load all votes at once into memory (as fetching all the table in a resultset). You can always use LIMIT clause to narrow your query results.

    • 0