[CliptonHeist]

Why use auto-incremented value when you have a completely unique identifier to use already? Not only does using steamids for primary keys make sure that there is never a duplicated player row inserted into the db but it makes updating records simple since you never have to worry about a client index being invalid.

[Dragokas]

Ok, I understand you now.
Look like you have no problems in that case. I hope you store the last ID used for autoincrementation in the separate table, so it will not be duplicated, as CliptonHeist said.

As about UserId - it's just a reference. Using it (with GetClientOfUserId()), you can ensure it is point to valid ClientId (the reference was initially created from). If you would pass ClientId instead (in timer callback) you are risking that while the timer was ticking, that ClientId is disconnected and new player took the same place (same ClientId), so when the timer triggers, it will affect the wrong player.

[McSnaggit]

@CliptonHeist I use an AI value because I don't think foreign keys kan be characters, like the steamID2. I do use the steamId to verify if the user exists but I use the id of the table as a foreign key. So I won't ever have duplicate entries.

Thanks all!

PS: How can I solve this post?

[Dragokas]

Press "edit" button on the first post, go to "Advanced mode" => change value in combobox => save.

[CliptonHeist]

Originally Posted by McSnaggit @CliptonHeist I use an AI value because I don't think foreign keys kan be characters, like the steamID2. I do use the steamId to verify if the user exists but I use the id of the table as a foreign key. So I won't ever have duplicate entries. Thanks all! PS: How can I solve this post?

Yes they absolutely can, any datatype in mysql can be used as a primary/foreign key lol. I would highly suggest reorganizing your database structure to use them to avoid headaches down the road.