Two Tables for Authentication?
Some of the sample web authentication setups I'm seeing involve a database with two tables -- one for holding user info like name and phone number and the other for holding username and password.
There must be a reason for this. Is it a more secure setup?
No it is not more secure, it is faster.
It is more convenient. Having narrow tables with fewer fields means faster lookups and inserts since lets bytes need to be transferred.
It is marginal really, IMO it is hardly worthwhile separating just username and password into a separate table.
I suppose this setup also makes it easier for individuals to have separate login accounts, but i guess that that is rarely needed.
Your info helps me better understand what the author might be thinking.