It would be useful for module writing for the users table to assign a unique id to each registered user. This way tables created by modules could reference the unique id instead of the full username.
usernames are more likely to remain constant across different software you want to integrate. Numbers are easier to compare than strings, so they can be used internally, but usernames are best when interfacing with external code.
As an example, my own website has a forum and chat in addition to PGV. Due to usernames being the same across the board, I can easily manage who's online for all 3 softwares, not to mention keeping passwords sychronized. If these programs only provided interfaces to the numeric id of the user, I'd have to hit the database a lot more.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1278885
Originator: NO
usernames are more likely to remain constant across different software you want to integrate. Numbers are easier to compare than strings, so they can be used internally, but usernames are best when interfacing with external code.
As an example, my own website has a forum and chat in addition to PGV. Due to usernames being the same across the board, I can easily manage who's online for all 3 softwares, not to mention keeping passwords sychronized. If these programs only provided interfaces to the numeric id of the user, I'd have to hit the database a lot more.