table structure, is this bad? (simple question)

[Yeodan]

So I'm making an mmorpg browser game.

 

I have a table that stores players and a lot of info about them.

 

Before anyone can login, they have to register, this is done with an activation code, is it bad to store this code in the players table? The code is just used 1 time to activate the account.

 

Or should I just make another table for activation that has the player name and activation code?

[Ken2k7]

You can create a user_accounts table that has the following:

 

user_accounts

id

name

password

activation_code

last_login

date_registered

gender?

etc.

 

Nothing really on players, but it's for a user account. In the players table, reference the user_accounts table by using the id field.