22.04.2013, 12:06
****** put it very simply and he's absolutely right. Actually, I have a similar system, I set it up like this.
Table for the master accounts, meaning the account the player logs in with.
Table for all the characters, the master account table has an ID associated with the account, this ID is also used in the character tables to decide which characters belong to a player. When the player logs in using his master account it presents him a dialog with all his characters. This way you have no virtually no limit on the amount of characters. (your way is using SQL incorrectly, you are then focussing on the weak points instead of what it is designed to do
).
Using table relations you can link the two tables together so when you delete one it doesn't cause a dead link. If you need an example, just tell me but I recommend you to search some of the terms on ******.
Table for the master accounts, meaning the account the player logs in with.
Table for all the characters, the master account table has an ID associated with the account, this ID is also used in the character tables to decide which characters belong to a player. When the player logs in using his master account it presents him a dialog with all his characters. This way you have no virtually no limit on the amount of characters. (your way is using SQL incorrectly, you are then focussing on the weak points instead of what it is designed to do
).Using table relations you can link the two tables together so when you delete one it doesn't cause a dead link. If you need an example, just tell me but I recommend you to search some of the terms on ******.