I'd start by asking if you want to use a database at all, and if so, what for.
One problem is that you seem to be using 'table' to mean a gaming table (4-legged object) on which a game of Mastermind might take place - you might not even be interested in databases and might have found your way to this forum by mistake, having no idea what it's about!
But I'll ignore that possibility, and assume that you are asking about databases.
If you ignored the online aspect, where a single server might need to manage several different games simultaneously, then a simple two-player mastermind game might just use program variables to store its data:
- the colours of the 4 hidden pegs
- the colours of the pegs in each row submitted as guesses
- the number of guesses so far
- etc.
An ongoing game of Mastermind can be viewed as having a current state (the variables described above), and you probably also want to know who the two players are.
If it's an online (web-based?) game, then there are two reasons why you would need to store the game state in something more persistent than program variables:
(1) if it's web-based, then most web-server programs only run in response to user requests, rather than continuously, so variables can't be remembered in the program
(2) you may have several games running simultaneously
For those reasons, you probably need to have a way of storing (or 'persisting') all the variables for each game, and a way of telling one game from another. You could use several methods for that, including flat files or a database.
If you used a database, you might want one or more tables, listing all active games and giving the variables for each game. That would be a fairly simple database design exercise.
Whether you also want a database (table) of known users (people who can play games of Mastermind) is another question, but it could easily be kept in the same database.
A 'chat' feature (where the setter can taunt the guesser) is clearly also an important feature of such a game.